From owner-freebsd-fs  Sun Feb 20  2:50:58 2000
Delivered-To: freebsd-fs@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4256337BA8E; Sun, 20 Feb 2000 02:50:56 -0800 (PST)
	(envelope-from bright@fw.wintelcom.net)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.9.3/8.9.3) id DAA22031;
	Sun, 20 Feb 2000 03:19:39 -0800 (PST)
Date: Sun, 20 Feb 2000 03:19:38 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: fs@freebsd.org
Cc: mckusick@freebsd.org
Subject: changing mount options still can cause damage?
Message-ID: <20000220031938.D21720@fw.wintelcom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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 op-
     eration 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]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message