From owner-freebsd-bugs Mon Mar 18 4: 6:46 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A538F37B41B; Mon, 18 Mar 2002 04:06:41 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Mar 2002 12:06:37 +0000 (GMT) Date: Mon, 18 Mar 2002 12:06:36 +0000 From: David Malone To: Roy Hooper Cc: cjc@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/35992: /etc/rc has no way to force fsck -y at next boot, corrupt filesystems with soft updates required manual intervention Message-ID: <20020318120636.GA47234@walton.maths.tcd.ie> References: <200203170935.g2H9ZwM95481@freefall.freebsd.org> <20020317133702.GA33770@walton.maths.tcd.ie> <040601c1ce19$4383a610$1e02070a@litebrite> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <040601c1ce19$4383a610$1e02070a@litebrite> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Mar 17, 2002 at 08:07:22PM -0500, Roy Hooper wrote: > > > Added documentation for the rc.early(8) script to -CURRENT. > > > > The main bug here is that fsck -p didn't detect the problem. Is a > > copy of the currupted filesystem still available? > > I found this fsck log in the nightly security check... It does look like -p > did indeed fail when I rebooted it. In the past it didn't detect it at all > and just skipped the fsck. I wonder if fsck marked the disk as clean at some stage when there was still an inconsistancy - that might explain it. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message