From owner-freebsd-current Sat Sep 19 20:15:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15300 for freebsd-current-outgoing; Sat, 19 Sep 1998 20:15:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.2.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15283 for ; Sat, 19 Sep 1998 20:15:52 -0700 (PDT) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.1.13]) by yonge.cs.toronto.edu with SMTP id <86568-12114>; Sat, 19 Sep 1998 23:15:14 -0400 Received: by qew.cs.toronto.edu id <37911-17305>; Sat, 19 Sep 1998 23:14:58 -0400 Subject: Re: softupdates & fsck From: David Holland To: current@FreeBSD.ORG Date: Sat, 19 Sep 1998 23:14:55 -0400 In-Reply-To: <199809192317.QAA11186@salsa.gv.tsc.tdk.com> from "Don Lewis" at Sep 19, 98 07:17:37 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Sep19.231458edt.37911-17305@qew.cs.toronto.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > } My suspicion is that the first fsck run is getting the link counts wrong > } when it repairs the filesystem. I've taked a look at the fsck code, but > } haven't gotten too far, mostly because the code is so well commented -- NOT! > > Yup, fsck is definitely screwing up the filesystem when it tries to repair > it. The following transcripts were all taken while running single-user > after a panic. > : > : > ** Phase 4 - Check Reference Counts > LINK COUNT DIR I=139883 OWNER=root MODE=40755 > SIZE=1024 MTIME=Sep 19 11:47 1998 COUNT 2 SHOULD BE 1 > ADJUST? no FWIW (probably not much) I was seeing almost the same behavior out of NetBSD's fsck about a month ago after using some broken fs code. This had messed up reference counts, so that when you removed a file, it thought it was still open forever and so it never cleared the inode. This made fsck unhappy on files, but *very* unhappy if you removed a directory. The symptoms were almost identical, down to fsck marking the fs clean when it actually wasn't. So I'm going to hypothesize that there's a long-standing bug in fsck here that something in softupdates is tickling. -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message