From owner-freebsd-bugs  Sat Jun 29  5:10: 8 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B7EB937B408
	for <freebsd-bugs@hub.freebsd.org>; Sat, 29 Jun 2002 05:10:06 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D0FE743E21
	for <freebsd-bugs@hub.freebsd.org>; Sat, 29 Jun 2002 05:10:04 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g5TCA4JU076519
	for <freebsd-bugs@freefall.freebsd.org>; Sat, 29 Jun 2002 05:10:04 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g5TCA3QM076518;
	Sat, 29 Jun 2002 05:10:03 -0700 (PDT)
Date: Sat, 29 Jun 2002 05:10:03 -0700 (PDT)
Message-Id: <200206291210.g5TCA3QM076518@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: David Schultz <dschultz@uclink.Berkeley.EDU>
Subject: Re: kern/28465: Enabling softupdates on a clean but active filesystem can panic the kernel
Reply-To: David Schultz <dschultz@uclink.Berkeley.EDU>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR kern/28465; it has been noted by GNATS.

From: David Schultz <dschultz@uclink.Berkeley.EDU>
To: freebsd-gnats-submit@FreeBSD.org, umesh@juniper.net,
	dima@unixfreak.org
Cc:  
Subject: Re: kern/28465: Enabling softupdates on a clean but active filesystem can panic the kernel
Date: Sat, 29 Jun 2002 05:00:07 -0700

 I suspect that after the filesystem is downgraded to read-only, there
 is still some dirty data in the buffer cache.  In that case, tunefs
 does the right thing by merely checking that the filesystem is mounted
 read-only; mount does the wrong thing by returning before syncing the
 filesystem.

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