Background fsck is broken

[Ruslan Ermilov]

On Wed, Dec 15, 2004 at 11:46:18AM +0100, Poul-Henning Kamp wrote:
> In message <20041215095901.GK25967 at ip.net.ua>, Ruslan Ermilov writes:
> >
> >--KjSGHOmKKB2VUiQn
> >Content-Type: text/plain; charset=us-ascii
> >Content-Disposition: inline
> >Content-Transfer-Encoding: quoted-printable
> >
> >Hi,
> >
> >Here's another fsck(8) buglet.  While booting single-user, / is
> >mounted read-only, and "fsck -p /" succeeds as expected.  While
> >remounting / read-only (e.g., after shutting down from multi-user
> >to single-user), it doesn't:
> 
> This is working as designed.
> 
> The way it works is that when you boot, the root filesystem opens
> the device (r=1, w=0, e=0) thereby permitting fsck to open the
> device for write.
> 
> When the root filesystem is upgraded to RW, the open is opgraded
> to (r=1,w=1,e=1) and writing via /dev/mumble is no longer permitted.
> 
> Architecturally the way we fsck the root filesystem is highly bogus
> and it would be much cleaner if mounted filesystems _always_ were
> fsck'ed through a snapshot, but there are a unknown code to be written
> to allow that to happen for the case where "unexpected softupdates
> inconsistencies" are found.
> 
Are you saying it's not possible to downgrade the open to
(r=1, w=0, e=0) when a file system is downgraded from R/W to R/O?


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041215/5c291217/attachment.bin