Date: Sat, 04 Dec 1999 01:04:12 +0800 From: Peter Wemm <peter@netplex.com.au> To: Doug Rabson <dfr@nlsystems.com> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, obrien@NUXI.com, freebsd-alpha@freebsd.org Subject: Re: mount & friends broken in -current! Message-ID: <19991203170412.A5AEF1CC8@overcee.netplex.com.au> In-Reply-To: Message from Doug Rabson <dfr@nlsystems.com> of "Thu, 02 Dec 1999 10:40:05 GMT." <Pine.BSF.4.10.9912021039420.325-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote:
> On Wed, 1 Dec 1999, Andrew Gallatin wrote:
>
> >
> > 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 nex
t
> > > 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.
>
> I have a feeling that this was a side effect from PHK's most recent block
> device changes.
No, it predates even those. I've had this on and off for 6 months on some
of my machines. If phk has done anything, I strongly suspect he's merely
just irritated some already-lurking bug. Last time I looked at it, it looked
as though the MNT_RELOAD was getting lost or ignored or never issued.
I'd like folks to try something for me.. When this happens next time and
fsck reports the fs is 'clean' but mount says it's dirty, try a 'tunefs
-n disable /' (which forces a MNT_RELOAD) and see if you can then mount it.
It's fixed it for me in every case that I've seen so far.
Anyway, it was sporadic. Sometimes it happened, sometimes it didn't.
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991203170412.A5AEF1CC8>