Date: Mon, 21 Feb 2000 17:16:09 -0800 From: Kirk McKusick <mckusick@flamingo.McKusick.COM> To: Alfred Perlstein <bright@wintelcom.net> Cc: fs@freebsd.org, jkh@freebsd.org Subject: Re: changing mount options still can cause damage? Message-ID: <200002220116.RAA18831@flamingo.McKusick.COM> In-Reply-To: Your message of "Mon, 21 Feb 2000 17:44:44 PST." <20000221174444.W21720@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Date: Mon, 21 Feb 2000 17:44:44 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: Kirk McKusick <mckusick@flamingo.McKusick.COM>
Cc: fs@freebsd.org, jkh@freebsd.org
Subject: Re: changing mount options still can cause damage?
* Kirk McKusick <mckusick@flamingo.McKusick.COM> [000221 16:30] wrote:
>
> Switching between read-only and read-write should never cause filesystem
> corruption. Running async can certainly lead to corruption if the
> system crashes. There is an indeterminate period of time after the
> system has been switched from async to sync before it will be stable
> again, but that period will rarely be more than a minute or two. The
> act of switching between sync and async should not cause corruption.
> It is just the inherent risk of corruption while running async.
>
> Kirk McKusick
Then I vote to remove it, there's no reason we should be slandering
ourselves in our own manpages, the async option already describes
the dangers pretty clearly.
May I axe it?
--
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
As far as I am concerned, you can axe it.
~Kirk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002220116.RAA18831>