From owner-freebsd-fs Tue Feb 22 18:45: 2 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 14A8537B849; Tue, 22 Feb 2000 18:44:59 -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 SAA22016; Tue, 22 Feb 2000 18:32:25 -0800 (PST) Message-Id: <200002230232.SAA22016@flamingo.McKusick.COM> To: Terry Lambert Subject: Re: changing mount options still can cause damage? Cc: bright@wintelcom.net (Alfred Perlstein), fs@freebsd.org, jkh@freebsd.org In-reply-to: Your message of "Wed, 23 Feb 2000 02:30:44 GMT." <200002230230.TAA27823@usr07.primenet.com> Date: Tue, 22 Feb 2000 18:32:25 -0800 From: Kirk McKusick Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A downgrade from read-write to read-only does a complete flush of the filesystem before setting the clean bit in the superblock. So, even if you have been running async before or even during the period that you do the downgrade to read-only, you will not trash the filesystem. I do not believe that you are lying to anybody by deleting the commentary about cycling between read-only and read-write. Appropriate warnings about async are called for, however the only warning necessary about cycling between sync and async is that the danger of async does not go away for several minutes after you have cycled to sync. ~Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message