From owner-freebsd-current Thu Jan 20 13:58:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2057B15318 for ; Thu, 20 Jan 2000 13:58:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA00569; Thu, 20 Jan 2000 22:57:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Still getting 'R/W mount of / denied ...' after valid fsck In-reply-to: Your message of "Thu, 20 Jan 2000 09:52:57 PST." <200001201752.JAA52389@apollo.backplane.com> Date: Thu, 20 Jan 2000 22:57:38 +0100 Message-ID: <567.948405458@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message