Date: Mon, 22 Nov 1999 14:57:39 +1000 From: Stephen McKay <syssgm@detir.qld.gov.au> To: Christopher Masto <chris@netmonger.net> Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Fsck follies Message-ID: <199911220457.OAA47173@nymph.detir.qld.gov.au> In-Reply-To: <19991121130020.A2369@netmonger.net> from Christopher Masto at "Sun, 21 Nov 1999 13:00:20 -0500" References: <199911211236.WAA27489@nymph.detir.qld.gov.au> <19991121130020.A2369@netmonger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 21st November 1999, Christopher Masto wrote: >On Sun, Nov 21, 1999 at 10:36:32PM +1000, Stephen McKay wrote: >> When the system came back up, fsck -p didn't like the vinum volume. >> No sweat, I ran it manually. There were many >> >> INCORRECT BLOCK COUNT I=<n> (4 should be 0) >> >> messages. I assumed this was an artifact of soft updates. The fsck >> completed successfully. >> >> Being paranoid, I reran fsck. This time it reported a number of >> unreferenced inodes (199 to be exact), and linked them in to lost+found. >> >> It is this last item that bothers me. When the first fsck completed, >> the filesystem should have been structurally correct. But it wasn't. >> A third fsck confirmed that 2 runs of fsck were enough. > >Presumably you are using vinum for mirroring? I have had to stop >doing so after trashing several filesystems. There are some serious >bugs that allow the plexes to get out of sync; as reads from a mirror >set are round-robin, this can be very bad. No, I was just striping them (4 x 660 MB disks, 96 KB interleave). Vinum had nothing to do with the problem. I was just reporting all the facts, just in case. I think there is a fault in fsck. Possibly it is because softupdates changed the rules. Having run md5 over the good copy and the broken (power failure interrupted) copy as well as everything in lost+found, I can say that no corrupted files survived, and everything in lost+found was a good copy of some file or other. So softupdates appears to be doing the right thing. But fsck didn't fix everything broken by the power interruption. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911220457.OAA47173>