From owner-freebsd-current@FreeBSD.ORG Tue Sep 22 03:32:23 2009 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 0B3841065670 for ; Tue, 22 Sep 2009 03:32:23 +0000 (UTC) (envelope-from johny-freebsd@earthmagic.org) Received: from ppp194-14.static.internode.on.net (ppp194-14.static.internode.on.net [59.167.194.14]) by mx1.freebsd.org (Postfix) with ESMTP id BAE098FC14 for ; Tue, 22 Sep 2009 03:32:22 +0000 (UTC) Received: from [192.168.2.4] (tornado.zone2.earthmagic.org [192.168.2.4]) by ppp194-14.static.internode.on.net (Postfix-MSA) with ESMTP id CD7BF66F22 for ; Tue, 22 Sep 2009 13:10:31 +1000 (EST) Message-ID: <4AB84026.7010908@earthmagic.org> Date: Tue, 22 Sep 2009 13:10:30 +1000 From: Johny Mattsson User-Agent: Thunderbird 2.0.0.23 (X11/20090919) MIME-Version: 1.0 To: freebsd-current References: <1253540159.15847.31.camel@bauer.cse.buffalo.edu> In-Reply-To: <1253540159.15847.31.camel@bauer.cse.buffalo.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 8.0-RC1 Available 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: Tue, 22 Sep 2009 03:32:23 -0000 Ken Smith wrote: > a patch set was committed by the people who handle porting ZFS to FreeBSD > that they felt makes ZFS production-ready. Hi there, I only loaded up -BETA4 over the weekend, and went through the extra hoops to get a ZFS root (and everything else) to give that a spin. Aside from the already-reported lock-order-reversals on zfs unmount, I ran into a slight issue when using freebsd-update to go to -RC1 --- It nuked my ZFS-aware /boot/loader and left me stranded at the loader prompt. Now this is quite arguably self-inflicted and now that I'm aware of it I can make sure I'm careful around it in the future, but is there any chance of having either a) the loader be ZFS-aware by default (especially if ZFS is now considered production-ready)? or b) have freebsd-update notice that /boot/loader has changed from the initial install and leave it alone (and maybe whinge about it)? Either way, good work on getting ZFS in! Cheers /Johny