Date: Mon, 18 Mar 2002 12:06:36 +0000 From: David Malone <dwmalone@maths.tcd.ie> To: Roy Hooper <rhooper@toybox.ca> 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> In-Reply-To: <040601c1ce19$4383a610$1e02070a@litebrite> References: <200203170935.g2H9ZwM95481@freefall.freebsd.org> <20020317133702.GA33770@walton.maths.tcd.ie> <040601c1ce19$4383a610$1e02070a@litebrite>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020318120636.GA47234>