From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 07:22:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8F82106564A; Wed, 19 Nov 2008 07:22:32 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 856B68FC0A; Wed, 19 Nov 2008 07:22:32 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (unknown [74.193.182.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 6DE8AA23F250; Wed, 19 Nov 2008 01:22:31 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id mAJ7Moen006171; Wed, 19 Nov 2008 01:22:50 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Wed, 19 Nov 2008 01:22:50 -0600 (CST) From: Wes Morgan To: Pawel Jakub Dawidek In-Reply-To: <20081117205526.GC1733@garage.freebsd.pl> Message-ID: References: <20081117205526.GC1733@garage.freebsd.pl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: New ZFS in the tree. 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, 19 Nov 2008 07:22:33 -0000 On Mon, 17 Nov 2008, Pawel Jakub Dawidek wrote: > Hi. > > So ZFS was updated from version 6 to 13. Be very careful when updating > your system if you use ZFS. The number of changes is huge and my > regression tests and manual tests I did only cover part of the entire > functionality. I'm hitting this at reboot, with a zfs root: zfs_vfsops.c:969 ZFS_LOG(0, "Force unmount is not supported, removing FORCE flag."); Followed by a "cannot unmount / (busy)" (however it shows up) error. Looking at the code, it looks like that message is simply to be expected...