From owner-freebsd-current@FreeBSD.ORG  Tue Dec  7 07:02:49 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 1781B16A4CE; Tue,  7 Dec 2004 07:02:49 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3E49243D55; Tue,  7 Dec 2004 07:02:48 +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 iB772lGq099085;
	Tue, 7 Dec 2004 08:02:47 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Ruslan Ermilov <ru@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 07 Dec 2004 00:54:33 +0200."
             <20041206225432.GA87510@ip.net.ua> 
Date: Tue, 07 Dec 2004 08:02:47 +0100
Message-ID: <99084.1102402967@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:49 -0000

In message <20041206225432.GA87510@ip.net.ua>, Ruslan Ermilov writes:

>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 /".

Fixed.

-- 
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.