From owner-freebsd-current Sun Nov 21 4:47:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 7D65B151D5 for ; Sun, 21 Nov 1999 04:47:19 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id WAA28526; Sun, 21 Nov 1999 22:46:48 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma028522; Sun, 21 Nov 99 22:46:40 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA13585 for ; Sun, 21 Nov 1999 22:36:34 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA25549 for ; Sun, 21 Nov 1999 22:36:33 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id WAA27489; Sun, 21 Nov 1999 22:36:32 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199911211236.WAA27489@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Fsck follies Date: Sun, 21 Nov 1999 22:36:32 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was giving vinum + softupdates a bit of a workout on 4 really old SCSI disks (Sun shoeboxes, if you must know) attached to an aha1542B. The rest of the machine is a Pentium 133 with 64MB of parity ram, a few more disks, and another aha1542B. It runs -current (about 10 days old now). I was copying a newer -current source tree onto the box when I lost power to my house for maybe half a second. Being foolish and shortsighted, I have no UPS. (An interesting side note: out of the 3 machines in use at the time, 2 of the keyboards locked up and required a power down to recover. I was unaware that keyboards could crash.) 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= (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. I seem to recall sagely advice from days gone by to always run fsck twice and sync thrice. I thought I could forget all that stuff nowadays. By the way, I saved the broken old source tree and compared it to the full tree. There were no unusual differences, except for the broken one being incomplete. So, if fsck were a little better, things would be fine. As good as you could expect, given a power failure. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message