Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Dec 2004 08:02:29 +0100
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Doug White <dwhite@gumbysoft.com>
Cc:        current@freebsd.org
Subject:   Re: NMOUNT/OMOUNT midway status 
Message-ID:  <99073.1102402949@critter.freebsd.dk>
In-Reply-To: Your message of "Mon, 06 Dec 2004 18:55:38 PST." <20041206185349.G23442@carver.gumbysoft.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20041206185349.G23442@carver.gumbysoft.com>, Doug White writes:
>On Tue, 7 Dec 2004, Ruslan Ermilov wrote:
>
>> Are you aware of the following problem?  On a recent
>> -CURRENT system, remounting / by fsck(8) is not possible:
>>
>> 	mount reload of '/' failed: Invalid argument
>>
>> This has been triggered by an unclean shutdown due to a
>> panic, but can also be reproduced easily by booting or
>> shutting down into single-user mode, having / mounted
>> read-only, and typing "fsck /".
>
>I got this today on one of my machines. It would seem that whatever in the
>kernel checks the clean bit isn't picking it up after fsck finishes.
>
>I wonder if this may be related to the ufs/ffs aliasing problem fixed
>earlier.

Fixed.  No it was slightly different.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99073.1102402949>