From root@rtfm.ziplink.net  Sat Apr  4 08:32:32 1998
Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04972
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 4 Apr 1998 08:32:30 -0800 (PST)
          (envelope-from root@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (rtfm [199.232.255.52])
	by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id QAA00656
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 4 Apr 1998 16:32:27 GMT
	(envelope-from root@rtfm.ziplink.net)
Received: (from root@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id LAA00999;
	Sat, 4 Apr 1998 11:32:26 -0500 (EST)
Message-Id: <199804041632.LAA00999@rtfm.ziplink.net>
Date: Sat, 4 Apr 1998 11:32:26 -0500 (EST)
From: Charlie Root <root@rtfm.ziplink.net>
Reply-To: mi@aldan.algebra.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: nitpicking on mount(8)
X-Send-Pr-Version: 3.2

>Number:         6209
>Category:       bin
>Synopsis:       No rw from ro if was not clean. fsck-ing does not help
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr  4 08:40:02 PST 1998
>Closed-Date:    Sat Apr 11 00:52:20 PDT 1998
>Last-Modified:  Sat Apr 11 00:54:05 PDT 1998
>Originator:     Mikhail Teterin
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
Virtual Estates, Inc.
>Environment:

	CURRENT as of Wed Mar 11 11:52:42 EST 1998

>Description:

	See below

>How-To-Repeat:

	For a non-clean partition:

	mount -o ro /partition # Succeeds with warning, as supposed to
	mount -u -o rw /partition # Fails as supposed to
	fsck /partition # Works and cleans things up. Sets the clean-flag
	mount -u -o rw /partition # Fails, which is now wrong

>Fix:
	
	umount /partition # Full umount is needed first
	mount /partition # Works fine
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Sat Apr 11 00:52:20 PDT 1998 
State-Changed-Why:  
You cannot do this with anything but the rootfs.  The chardev doesn't 
update the superblock in which the kernel holds a copy of in RAM. 
you must unmount, fsck, mount to fix this.  It is not impossible to 
make it so that it works the way you want it, but priority is zero+epsilon. 
>Unformatted:
