From owner-freebsd-current Sun Nov 21 10: 0:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id DAAD714DA8 for ; Sun, 21 Nov 1999 10:00:21 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id NAA02690; Sun, 21 Nov 1999 13:00:20 -0500 (EST) Message-ID: <19991121130020.A2369@netmonger.net> Date: Sun, 21 Nov 1999 13:00:20 -0500 From: Christopher Masto To: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: Fsck follies Mail-Followup-To: Stephen McKay , freebsd-current@FreeBSD.ORG References: <199911211236.WAA27489@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199911211236.WAA27489@nymph.detir.qld.gov.au>; from Stephen McKay on Sun, Nov 21, 1999 at 10:36:32PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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= (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. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message