Date: Sun, 17 Mar 2002 14:36:38 -0500 From: "Roy Hooper" <rhooper@toybox.ca> To: "David Malone" <dwmalone@maths.tcd.ie>, <cjc@FreeBSD.org> Cc: <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: <033201c1cdeb$10697580$1e02070a@litebrite> References: <200203170935.g2H9ZwM95481@freefall.freebsd.org> <20020317133702.GA33770@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry to say that it is not. If I encounter it again, i'll dd it up and gzip it (and open a new bug). I didn't think -p isn't supposed to actually examine the filesystem beyond the clean flag. As such the question is really how did the filesystem get corrupt yet keep the clean flag at the next boot? Perhaps a double hard-cold-reset could cause that -- that is exactly what happened at one point, possibly during an fsck. Perhaps when routines like dscheck detect errors, the dirty flag can be forced to be set and cause unmount to refuse to clear it? Roy -- Roy Hooper Project Manager & Senior UNIX Consultant Decisive Technologies Inc. ----- Original Message ----- From: "David Malone" <dwmalone@maths.tcd.ie> To: <cjc@FreeBSD.org> Cc: <rhooper@toybox.ca>; <freebsd-bugs@FreeBSD.org> Sent: Sunday, March 17, 2002 8:37 AM Subject: Re: misc/35992: /etc/rc has no way to force fsck -y at next boot, corrupt filesystems with soft updates required manual intervention > > 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? > > 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?033201c1cdeb$10697580$1e02070a>