From owner-freebsd-current@FreeBSD.ORG  Tue Dec  7 07:02:31 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1479516A4CF; Tue,  7 Dec 2004 07:02:31 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5CBA143D5E; Tue,  7 Dec 2004 07:02:30 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB772T1F099074;
	Tue, 7 Dec 2004 08:02:29 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Doug White <dwhite@gumbysoft.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 06 Dec 2004 18:55:38 PST."
             <20041206185349.G23442@carver.gumbysoft.com> 
Date: Tue, 07 Dec 2004 08:02:29 +0100
Message-ID: <99073.1102402949@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: current@freebsd.org
Subject: Re: NMOUNT/OMOUNT midway status 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2004 07:02:31 -0000

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.