<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: File system corruption in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014310#M613492</link>
    <description>Replacement disk was faulty too.  Restored onto  another disk.</description>
    <pubDate>Thu, 16 Nov 2006 08:38:16 GMT</pubDate>
    <dc:creator>John Kelly_3</dc:creator>
    <dc:date>2006-11-16T08:38:16Z</dc:date>
    <item>
      <title>File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014300#M613482</link>
      <description>I'm trying to recover from a filesystem corruption situation.  We were getting inode errors in the syslog from a filesystem and by excluding the faulty files, I managed to run an fbackup.  I had the disk replaced and recreated the filesystem.  However when I frecover, the filesystem is corrupt.  &lt;BR /&gt;fsck -y -o full -y /dev/vg01/lvol2 &lt;BR /&gt;doesn't fix it.&lt;BR /&gt;I get loads of &lt;BR /&gt;fileset 999 primary inode 95306 unreferenced file, reconnect? (ynq)y&lt;BR /&gt;fileset 999 primary inode 95307 unreferenced file, reconnect? (ynq)y&lt;BR /&gt;fileset 999 primary inode 95308 unreferenced file, reconnect? (ynq)y&lt;BR /&gt;&lt;BR /&gt;Any suggestions?&lt;BR /&gt;It is on HPUX 11.0, A500-7X.</description>
      <pubDate>Thu, 16 Nov 2006 01:18:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014300#M613482</guid>
      <dc:creator>John Kelly_3</dc:creator>
      <dc:date>2006-11-16T01:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014301#M613483</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;newfs the filesystem&lt;BR /&gt;Restore all data.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 16 Nov 2006 01:47:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014301#M613483</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-11-16T01:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014302#M613484</link>
      <description>I'm getting these errors AFTER I've&lt;BR /&gt;replaced the disk,&lt;BR /&gt;created the LV&lt;BR /&gt;run newfs&lt;BR /&gt;frecover'ed the data&lt;BR /&gt;&lt;BR /&gt;Any suggestions?</description>
      <pubDate>Thu, 16 Nov 2006 01:53:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014302#M613484</guid>
      <dc:creator>John Kelly_3</dc:creator>
      <dc:date>2006-11-16T01:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014303#M613485</link>
      <description>Johan,&lt;BR /&gt;&lt;BR /&gt;Why cant you try an fsck with an alternate superblock copy.&lt;BR /&gt;&lt;BR /&gt;Alternate superblock copies will be  availble&lt;BR /&gt;in /etc/sbtab&lt;BR /&gt;&lt;BR /&gt;then do a fsck with -b option i hope .&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Siva</description>
      <pubDate>Thu, 16 Nov 2006 02:53:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014303#M613485</guid>
      <dc:creator>siva0123</dc:creator>
      <dc:date>2006-11-16T02:53:51Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014304#M613486</link>
      <description>The command should be something like this.&lt;BR /&gt;&lt;BR /&gt;fsck -F filesystemtype -b alternatesuperblockcopy -o full&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Siva</description>
      <pubDate>Thu, 16 Nov 2006 02:59:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014304#M613486</guid>
      <dc:creator>siva0123</dc:creator>
      <dc:date>2006-11-16T02:59:03Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014305#M613487</link>
      <description>I'll give the fsck suggestion a try once I finish another restore.&lt;BR /&gt;First restore was onto a mirrored LV. - faulty&lt;BR /&gt;I split the mirror...&lt;BR /&gt;Second restore was to LV on new disk. - faulty&lt;BR /&gt;Trying onto the second disk now.&lt;BR /&gt;During previous restores there were errors like this (which was why I ran fsck after the restore) -&lt;BR /&gt;vxfs: mesg 008: vx_direrr - /volumes file system inode 16195 block 1946498 error 6&lt;BR /&gt;&lt;BR /&gt;Still no disk errors and there weren't any stale extents.</description>
      <pubDate>Thu, 16 Nov 2006 03:05:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014305#M613487</guid>
      <dc:creator>John Kelly_3</dc:creator>
      <dc:date>2006-11-16T03:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014306#M613488</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;While you do the restore , &lt;BR /&gt;&lt;BR /&gt;Please go thorugh this thread.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=945777" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=945777&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;siva</description>
      <pubDate>Thu, 16 Nov 2006 03:13:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014306#M613488</guid>
      <dc:creator>siva0123</dc:creator>
      <dc:date>2006-11-16T03:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014307#M613489</link>
      <description>fsck -F vxfs -b alternatesuperblockcopy -o full /dev/vg01/lvol2&lt;BR /&gt;fsck: illegal option -- b&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;:-(&lt;BR /&gt;&lt;BR /&gt;Still running the third restore</description>
      <pubDate>Thu, 16 Nov 2006 03:20:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014307#M613489</guid>
      <dc:creator>John Kelly_3</dc:creator>
      <dc:date>2006-11-16T03:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014308#M613490</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;I hope you used the following command&lt;BR /&gt;&lt;BR /&gt;fsck -F vxfs -b XXX -o full /dev/vg01/rlo\vol2&lt;BR /&gt;&lt;BR /&gt;where XXX=&amp;gt;Alternate superblock copy no which you got from /etc/sbtab file&lt;BR /&gt;&lt;BR /&gt;If that have failed i'm having a feeling that -b option is supported for only root filesystem /dev/vg00/rlvol1 .&lt;BR /&gt;&lt;BR /&gt;I've tested this before successfully in /dev/vg00/lvol1&lt;BR /&gt;&lt;BR /&gt;Let me confirm.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;siva</description>
      <pubDate>Thu, 16 Nov 2006 03:53:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014308#M613490</guid>
      <dc:creator>siva0123</dc:creator>
      <dc:date>2006-11-16T03:53:16Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014309#M613491</link>
      <description>Ok, I finished the restore onto the last remaining disk and it was successful with no filesystem errors.  So the unlikely conclusion is that the replacement disk was as faulty as the original one.&lt;BR /&gt;That is thanks to the cheap third-party hardware support company.&lt;BR /&gt;&lt;BR /&gt;Genuine thanks to all who responded for your time.</description>
      <pubDate>Thu, 16 Nov 2006 08:33:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014309#M613491</guid>
      <dc:creator>John Kelly_3</dc:creator>
      <dc:date>2006-11-16T08:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: File system corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014310#M613492</link>
      <description>Replacement disk was faulty too.  Restored onto  another disk.</description>
      <pubDate>Thu, 16 Nov 2006 08:38:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-system-corruption/m-p/5014310#M613492</guid>
      <dc:creator>John Kelly_3</dc:creator>
      <dc:date>2006-11-16T08:38:16Z</dc:date>
    </item>
  </channel>
</rss>

