From owner-freebsd-current@FreeBSD.ORG Wed Aug 31 21:46:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 659AB16A421 for ; Wed, 31 Aug 2005 21:46:17 +0000 (GMT) (envelope-from freebsd@powered.net) Received: from relay.xpto.com (xpto.brasiltelecom.com.br [200.181.14.30]) by mx1.FreeBSD.org (Postfix) with SMTP id 7410343D46 for ; Wed, 31 Aug 2005 21:46:15 +0000 (GMT) (envelope-from freebsd@powered.net) Received: (qmail 39406 invoked by uid 1009); 31 Aug 2005 21:43:18 -0000 Received: from unknown (HELO ?10.61.218.95?) (10.61.218.95) by relay.xpto.com with SMTP; 31 Aug 2005 21:43:18 -0000 Message-ID: <431624D4.5080800@powered.net> Date: Wed, 31 Aug 2005 18:44:52 -0300 From: Rainer Alves User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050828) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 6.0-BETA3: ext2fs: if mounted at shutdown, fsck at next boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 31 Aug 2005 21:46:17 -0000 Actually there's a workaround for this... add the following near the end of /etc/rc.shutdown: Sure, it isn't the perfect solution, but it works. Rainer Alves BrasilTelecom ----------- # Insert other shutdown procedures here extfs=`eval mount | grep ext2fs | awk '{print $1 }'` for _elem in $extfs; do echo -n "Unmounting ext2/ext3 filesystems: " umount -f $_elem echo -n "$_elem " done ----------- Matthias Andree wrote: >See Subject - this bug has already haunted FreeBSD 5 and still persists >in FreeBSD 6.0: shutting down FreeBSD 5 or 6 with a mounted ext2fs file >system prevents proper synching of the super blocks (vnode count remains >nonzero, until kernel gives up), so all file systems that were mounted >are fsck'd at next reboot, UFS, UFS2, ext2fs, doesn't matter. > >Someone please check the ext2fs locking. > > >