From archie@packetdesign.com  Wed May  2 16:43:26 2001
Return-Path: <archie@packetdesign.com>
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by hub.freebsd.org (Postfix) with ESMTP id B955737B424
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  2 May 2001 16:43:26 -0700 (PDT)
	(envelope-from archie@packetdesign.com)
Received: from bubba.packetdesign.com (bubba.packetdesign.com [192.168.0.223])
	by mailman.packetdesign.com (8.11.0/8.11.0) with ESMTP id f42NhQ258646
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 2 May 2001 16:43:26 -0700 (PDT)
	(envelope-from archie@packetdesign.com)
Received: (from archie@localhost)
	by bubba.packetdesign.com (8.11.3/8.11.1) id f42NhQv61898;
	Wed, 2 May 2001 16:43:26 -0700 (PDT)
	(envelope-from archie)
Message-Id: <200105022343.f42NhQv61898@bubba.packetdesign.com>
Date: Wed, 2 May 2001 16:43:26 -0700 (PDT)
From: Archie Cobbs <archie@packetdesign.com>
Reply-To: archie@packetdesign.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: remounting a r/w filesystem read-only causes shutdown problem
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         27044
>Category:       kern
>Synopsis:       remounting a r/w filesystem read-only causes shutdown problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 02 16:50:01 PDT 2001
>Closed-Date:    Sun Feb 10 22:25:54 PST 2002
>Last-Modified:  Sun Feb 10 22:28:10 PST 2002
>Originator:     Archie Cobbs
>Release:        FreeBSD 4.3-RELEASE i386
>Organization:
Packet Design
>Environment:
System: FreeBSD bubba.packetdesign.com 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Thu Apr 26 15:28:39 PDT 2001 root@bubba.packetdesign.com:/usr/obj/usr/src/sys/BUBBA i386


>Description:

	Sometimes FreeBSD has problems "syncing buffers" when shutting
	down, and then it "gives up". I'm not sure why this happens, but
	the practical result is an unclean (and possibly screwed up)
	filesystem at the next reboot, so it's definitely a bad thing.

	I can reproducibly get this to happen by mounting a filesystem
	read-write, mucking with some files, and then remounting
	it read-only (ie., updating the mount: "mount -u -o ro"), and
	then rebooting.

>How-To-Repeat:

	mount /foo
	cp -R /var /foo
	mount -u -o ro /foo
	reboot

	By the way, /foo has soft updates enabled.

>Fix:

	Skip the "mount -u -o ro /foo" step.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mckusick 
State-Changed-When: Sun Feb 10 22:25:54 PST 2002 
State-Changed-Why:  
This bug was fixed by revision 1.167 to /sys/ufs/ffs/ffs_vfsops.c. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27044 
>Unformatted:
