From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 22:59:41 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00D3C106564A for ; Wed, 8 Jun 2011 22:59:41 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BAE828FC12 for ; Wed, 8 Jun 2011 22:59:40 +0000 (UTC) Received: by vws18 with SMTP id 18so1133308vws.13 for ; Wed, 08 Jun 2011 15:59:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.177.205 with SMTP id bj13mr14786vcb.39.1307573979505; Wed, 08 Jun 2011 15:59:39 -0700 (PDT) Received: by 10.220.80.144 with HTTP; Wed, 8 Jun 2011 15:59:39 -0700 (PDT) X-Originating-IP: [93.221.173.86] In-Reply-To: <20110608225556.GQ7064@alchemy.franken.de> References: <4DECB197.8020102@FreeBSD.org> <20110608211203.GA35440@alchemy.franken.de> <20110608225556.GQ7064@alchemy.franken.de> Date: Thu, 9 Jun 2011 00:59:39 +0200 Message-ID: From: "C. P. Ghost" To: Marius Strobl Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 22:59:41 -0000 On Thu, Jun 9, 2011 at 12:55 AM, Marius Strobl wrote: > On Thu, Jun 09, 2011 at 12:46:19AM +0200, C. P. Ghost wrote: >> On Wed, Jun 8, 2011 at 11:12 PM, Marius Strobl >> wrote: >> > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: >> >> Hi, >> >> >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741) >> >> >> >> New major features: >> >> >> >> - data deduplication >> >> - triple parity RAIDZ (RAIDZ3) >> >> - zfs diff >> >> - zpool split >> >> - snapshot holds >> >> - zpool import -F. Allows to rewind corrupted pool to earlier >> >> ? transaction group >> >> - possibility to import pool in read-only mode >> >> >> >> For updating, there is a compatibility layer so that in the update phase >> >> most functionality of the new zfs binaries can be used with the old >> >> kernel module and old zfs binaries with the new kernel module. >> > >> > Beware that the compatibility layer is known broken on big-endian >> > architectures, i.e. powerpc64 and sparc64. >> >> Thanks for the heads-up! I was just about to update a couple of sparc64 >> machines here. Fortunately, the only ZFS file systems there are external >> file systems (no /, /usr, /var etc...), so it's gonna be painless, I suppose. >> But what about other layouts? Does it mean that an installkernel, reboot, >> and installworld won't work? > > No, using the old zfs binaries with the new kernel module triggers the > problem. Using the new zfs binaries with the new kernel module works > (at least with CURRENT) so you'd need disregard everything that is > documented and do what is not guaranteed to work but usually also does, > i.e. do installkernel, installworld and then reboot. Ah, yes, that's what I expected. Thank you! -cpghost. -- Cordula's Web. http://www.cordula.ws/