From owner-freebsd-fs Mon Feb 21 16:37:35 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 0B81F37B529 for ; Mon, 21 Feb 2000 16:37:24 -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 QAA18690; Mon, 21 Feb 2000 16:00:52 -0800 (PST) Message-Id: <200002220000.QAA18690@flamingo.McKusick.COM> To: Alfred Perlstein Subject: Re: changing mount options still can cause damage? Cc: fs@freebsd.org In-reply-to: Your message of "Sun, 20 Feb 2000 03:19:38 PST." <20000220031938.D21720@fw.wintelcom.net> Date: Mon, 21 Feb 2000 16:00:51 -0800 From: Kirk McKusick Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Date: Sun, 20 Feb 2000 03:19:38 -0800 From: Alfred Perlstein To: fs@freebsd.org Cc: mckusick@freebsd.org Subject: changing mount options still can cause damage? Is it true that we can still cause major damage to filesystems that are moved from read-only to read-write or noasync <-> async? >From the mount manpage: -- BUGS It is possible for a corrupted file system to cause a crash. Switching a filesystem back and forth between asynchronous and normal operation or between read/write and read/only access using ``mount -u'' may gradually bring about severe filesystem corruption. -- The first bug is understandable, but personally I've never seen the second happen, is this still a real problem? If not I'd like to remove it. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message