From owner-freebsd-stable@FreeBSD.ORG  Fri Jun  3 02:00:19 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@FreeBSD.org
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7645B16A41C
	for <freebsd-stable@FreeBSD.org>; Fri,  3 Jun 2005 02:00:19 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F60743D1D
	for <freebsd-stable@FreeBSD.org>; Fri,  3 Jun 2005 02:00:18 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j53209PW004757;
	Thu, 2 Jun 2005 19:00:13 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200506030200.j53209PW004757@gw.catspoiler.org>
Date: Thu, 2 Jun 2005 19:00:09 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: mkb@incubus.de
In-Reply-To: <429FB785.8030102@incubus.de>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: freebsd-stable@FreeBSD.org, yuval_levy@yahoo.com
Subject: Re: filesystems not properly unmounted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2005 02:00:20 -0000

On  3 Jun, Matthias Buelow wrote:
> Don Lewis wrote:
> 
>> Nope, the ext2fs problem is different.  It is caused by ext2fs holding
>> persistent references to disk buffers that causes the kernel shutdown
>> code to to think that not all the dirty buffers have been written to
>> disk and skip unmounting all the file systems.
> 
> Can't that be changed in a way that the kernel checks that in a
> per-filesystem granularity instead of seemingly global?  I mean, I can
> understand that a marginal ext2 fs driver can cause problems with ext2
> filesystems, but affecting other filesystems aswell in such a way is not
> nice.

That might help to an extent, but would not eliminate the problem.  Any
file systems between root and the mount point of the ext2 file system
would be busy and would not be able to be unmounted.  They would still
be marked dirty and would need to be fsck'ed after the reboot.