From owner-freebsd-bugs Sun Mar 17 5:37:18 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 D229D37B404; Sun, 17 Mar 2002 05:37:10 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Mar 2002 13:37:03 +0000 (GMT) Date: Sun, 17 Mar 2002 13:37:02 +0000 From: David Malone To: cjc@FreeBSD.org Cc: rhooper@toybox.ca, 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: <20020317133702.GA33770@walton.maths.tcd.ie> References: <200203170935.g2H9ZwM95481@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200203170935.g2H9ZwM95481@freefall.freebsd.org> 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 > 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