From owner-freebsd-current Thu Jan 20 20:43:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id C390314D18 for ; Thu, 20 Jan 2000 20:43:49 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 28060 invoked from network); 21 Jan 2000 04:33:32 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 21 Jan 2000 04:33:32 -0000 Date: Fri, 21 Jan 2000 15:33:30 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Poul-Henning Kamp Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Still getting 'R/W mount of / denied ...' after valid fsck In-Reply-To: <567.948405458@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jan 2000, Poul-Henning Kamp wrote: > In message <200001201752.JAA52389@apollo.backplane.com>, Matthew Dillon writes: > > > I am still getting 'R/W mount of / denied' failures when rebooting a > > crashed -current machine. It thinks / is dirty but the fsck on it ran > > just fine. If I immediately /sbin/reboot again the machine comes up > > normally. > > fsck fails to remount and fails to tell that, so despite the fact > that the fs on the disk is clean the kernel doesn't get told. > > I belive Paul Saab is working on some improvements to fsck which > will help this... fsck is supposed to be improved already, but the improvements may have broken the (misconfigured) case where the root device is still a bdev. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message