From owner-freebsd-alpha  Wed Dec  1 18:50: 8 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id B0EF414FA8
	for <freebsd-alpha@FreeBSD.ORG>; Wed,  1 Dec 1999 18:50:03 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id VAA18374;
	Wed, 1 Dec 1999 21:47:53 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA65267;
	Wed, 1 Dec 1999 21:47:23 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed,  1 Dec 1999 21:47:23 -0500 (EST)
To: obrien@NUXI.com
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: mount & friends broken in -current!
In-Reply-To: <19991201182901.F29334@relay.nuxi.com>
References: <14405.37232.135805.78500@grasshopper.cs.duke.edu>
	<19991201161053.B84520@dragon.nuxi.com>
	<14405.51797.652995.942415@grasshopper.cs.duke.edu>
	<19991201182901.F29334@relay.nuxi.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14405.56663.383906.364548@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


David O'Brien writes:
 > On Wed, Dec 01, 1999 at 08:26:49PM -0500, Andrew Gallatin wrote:
 > >  > I'm not having those problems, but is anybody else experiencing the
 > >  > situation where on every boot one gets:
 > >  > 
 > >  >     WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck
 > > 
 > > This is on *every* reboot? Is there a chance / is not really clean?  
 > > Can you do a mount -uf / ?
 > 
 > Yep, *every* reboot.  When it occurs every thing but / is already
 > mounted.  I can manually do a ``fsck /'' and that works.  But on the next
 > reboot it does not help.
 > 

Hmm.. I think I'll bow out at this point.  All I can say is that it
seems damned strange that fsck -p is not marking / clean when it
finishes, but fsck / is. That's not happening here.  my fsck is from
over the weekend.

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message