From owner-freebsd-current@FreeBSD.ORG Sat Nov 29 04:59:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7031716A4CE for ; Sat, 29 Nov 2003 04:59:04 -0800 (PST) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76E2643F75 for ; Sat, 29 Nov 2003 04:59:02 -0800 (PST) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1])4CD4714BA1 for ; Sat, 29 Nov 2003 13:59:01 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id A68BE96FDB; Sat, 29 Nov 2003 13:58:59 +0100 (CET) To: Bruce Evans In-Reply-To: <20031127214229.O78318@gamplex.bde.org> (Bruce Evans's message of "Thu, 27 Nov 2003 21:53:35 +1100 (EST)") References: <20031126183744.GA9140@merlin.emma.line.org> <1069926206.891.3.camel@shoeserv.freebsd> <20031127214229.O78318@gamplex.bde.org> From: Matthias Andree Date: Sat, 29 Nov 2003 13:58:59 +0100 Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-current@freebsd.org cc: Stefan Ehmann Subject: 5.2-BETA: file system bugs considered harmful (was: 5.2-BETA: giving up on 4 buffers) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2003 12:59:04 -0000 Bruce Evans writes: > I'm not sure if the problem is known for the read-only case. It is > the same problem as in the read-write case. ext2fs hangs onto buffers, > so shutdown cannot tell if it can look at the buffers and considers > them to be busy. Then since shutdown cannot tell if it synced all dirty > buffers or which buffers are associated with which file systems, it > doesn't unmount any file systems and all dirty file systems that aren't > unmounted before shutdown are left dirty. Read-only-mounted ext2fs file > systems aren't left dirty but they break cleaning of other file systems. Either way, I consider the underlying bugs harmful. I tried to modify ext2 files, could read-write mount the partition, could modify the files and sync, but when I tried to mount -u -r the ext2 partition or umount it, I got a busy condition, and after reboot, the changes were lost, and a while later (an hour or so) the machine panicked in vinvalbuf(). Needless to say that after that, the machine fsck'd the whole disk (all partitions) and, worse, my root partition was damaged, files missing. I had run make installworld prior to the panic. My root partition is a regular noasync UFS1, /usr and /var are softupdates UFS2. Because of this damage, I consider the underlying file system bugs, whether in ext2fs or outside, to be harmful. I'm not claiming they're IN ext2fs (because of the ufs single-user fsck, reboot problem) but they can be triggered through ext2fs. Something's not quite right. -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95