Date: Wed, 2 May 2001 16:43:26 -0700 (PDT) From: Archie Cobbs <archie@packetdesign.com> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/27044: remounting a r/w filesystem read-only causes shutdown problem Message-ID: <200105022343.f42NhQv61898@bubba.packetdesign.com>
next in thread | raw e-mail | index | archive | help
>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: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 02 16:50:01 PDT 2001 >Closed-Date: >Last-Modified: >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: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105022343.f42NhQv61898>