From owner-freebsd-stable@FreeBSD.ORG  Thu Jun  2 23:53:55 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 87C0216A41C
	for <freebsd-stable@FreeBSD.org>; Thu,  2 Jun 2005 23:53:55 +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 4C40243D1D
	for <freebsd-stable@FreeBSD.org>; Thu,  2 Jun 2005 23:53:55 +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 j52NrkEH004579;
	Thu, 2 Jun 2005 16:53:50 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200506022353.j52NrkEH004579@gw.catspoiler.org>
Date: Thu, 2 Jun 2005 16:53:46 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: cswiger@mac.com
In-Reply-To: <363CBD31-8CA6-41F7-99D2-E11BC5D84FC2@mac.com>
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: Thu, 02 Jun 2005 23:53:55 -0000

On  2 Jun, Charles Swiger wrote:
> On Jun 2, 2005, at 4:56 PM, yuval levy wrote:
>>> If it's a pain to remeber, maybe try sticking
>>> something in rc.shutdown?
>>
>> Thank you for trying to help, but I do not find this
>> reply helpful. That's a quick and dirty fix, not a
>> solution.
> [ ...car analogy snipped... ]
>> Quick and dirty fixes are ok for the short term, but
>> this issue has been around for too long. I wish I had
>> the knowledge to fix it...
> 
> There's a discussion on -current called "Re: [RFC] [PATCH] VM & VFS  
> changes" which may help resolve the issue of unmounting and flushing  
> the tree of filesystems more cleanly, which you should look into and  
> be willing to test as code comes out.


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.