From owner-freebsd-current@FreeBSD.ORG  Tue Dec  7 02:55:38 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 89C1316A4CE; Tue,  7 Dec 2004 02:55:38 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5004743D58; Tue,  7 Dec 2004 02:55:38 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 4089C72DD4; Mon,  6 Dec 2004 18:55:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id 3E0E272DCB;
	Mon,  6 Dec 2004 18:55:38 -0800 (PST)
Date: Mon, 6 Dec 2004 18:55:38 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: Ruslan Ermilov <ru@freebsd.org>
In-Reply-To: <20041206225432.GA87510@ip.net.ua>
Message-ID: <20041206185349.G23442@carver.gumbysoft.com>
References: <90140.1102367413@critter.freebsd.dk>
	<20041206225432.GA87510@ip.net.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Poul-Henning Kamp <phk@phk.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 02:55:38 -0000

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.

--
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org