From owner-freebsd-fs Mon Feb 21 17:20:44 2000 Delivered-To: freebsd-fs@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id DC68D37B565; Mon, 21 Feb 2000 17:20:41 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id RAA18831; Mon, 21 Feb 2000 17:16:10 -0800 (PST) Message-Id: <200002220116.RAA18831@flamingo.McKusick.COM> To: Alfred Perlstein Subject: Re: changing mount options still can cause damage? Cc: fs@freebsd.org, jkh@freebsd.org In-reply-to: Your message of "Mon, 21 Feb 2000 17:44:44 PST." <20000221174444.W21720@fw.wintelcom.net> Date: Mon, 21 Feb 2000 17:16:09 -0800 From: Kirk McKusick Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Date: Mon, 21 Feb 2000 17:44:44 -0800 From: Alfred Perlstein To: Kirk McKusick Cc: fs@freebsd.org, jkh@freebsd.org Subject: Re: changing mount options still can cause damage? * Kirk McKusick [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