Date: Wed, 23 Feb 2000 08:02:16 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Alfred Perlstein <alfred@FreeBSD.org> Cc: Luoqi Chen <luoqi@watermarkgroup.com>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/sbin/mount mount.8 Message-ID: <Pine.BSF.4.21.0002230743070.3059-100000@alphplex.bde.org> In-Reply-To: <20000222115057.A21720@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Feb 2000, Alfred Perlstein wrote:
> * Luoqi Chen <luoqi@watermarkgroup.com> [000222 08:18] wrote:
> > Even if we fixed this one, we are not sure if there isn't any other problem
> > left that would compromise filesystem integrity (remember this part of the
> > code is barely tested). I think a warning label is still warranted.
>
> I agree, although the old one was a bit hysterical, is this truthful
> and complete:
>
> Downgrading a filesystem from read-write to read-only may cause
^ mount status
> filesystem corruption and therefore should be avoided.
> .Pp
> It may take a few moments for a filesystem going from async to sync or
^^^^^^^
> noasync to become fully safe with regard to consistancy after the option
^^^^^^^^^^^ consistency
> has been toggled.
Delete "sync or". noasync != sync (sync gives synchronous data updates).
The second paragraph is mostly FUD. I wouldn't add it. fs_flushfiles()
should flush all delayed writes, and it seems to do so (it does a
VOP_FSYNC(..., MNT_WAIT) to flush the metadata). Therefore, the
filesystem should be safe when `mount -u -o noasync ...' returns.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0002230743070.3059-100000>