[BUGA] looking for a better fsck

[Wilkinson, Alex]

    0n Sun, May 07, 2006 at 01:30:35PM +0930, Phil Kernick wrote: 

    >I have a root disk that for reasons best known to itself got somewhat
    >corrupted.  UFS2 on FreeBSD 5.5beta4.
    >
    >If I reboot and launch fixit from the install CD and...
    >
    ># fsck_ffs -y /dev/ad0s1a
    >
    >It comes up clean.  (I know, -y is scary and dangerous :-)
    >
    >But after doing some intensive disk activity, I get things like this:
    >May  7 11:19:52 kernel: bad block -1, ino 1979583
    >May  7 11:19:52 kernel: pid 952 (rm), uid 0 inumber 1979583 on /: bad block
    >
    >Somehow inode 1979583 ends up a with a bad block in it (probably from the
    >corruption that occurred a while back) and fsck didn't find it.
    >
    >I'm looking for a better fsck that will actually check the blocks in all the
    >inodes.
    >
    >According to fsck_ffs(8) it checks for:
    >     2.   Blocks claimed by an inode outside the range of the file system.
    >
    >But empirical evidence suggests that this is unlikely, inaccurate or incomplete.

In HEAD /usr/src/tools/tools/recoverdisk may help.

-aW