From owner-freebsd-current@FreeBSD.ORG Thu Feb 28 00:37:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E40C1FB5; Thu, 28 Feb 2013 00:37:48 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) by mx1.freebsd.org (Postfix) with ESMTP id CEEA8D6A; Thu, 28 Feb 2013 00:37:48 +0000 (UTC) Received: from epsilon.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 3FB62AFCD; Wed, 27 Feb 2013 16:37:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1362011868; bh=nCQPV1yG7AUiUV7Okvznpwg/uDf6C/sgHvOiOXz6u3k=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=2UwD7a8lNo07tRJqsszV5E+7/RwIhbydKu9ZjAtCztVg7B9L5urwTvjU/boZ8LOA2 g6Ix7aHC18/ll+lyL6MdZqC+S8Une1Ymvftf5t1YDJ1UdfXIyBzNxmmDD8WYoCkIla 6891FfLvyGlJM7Xmv+wBR1cauL4iPWLxYfZG6PRk= Message-ID: <512EA6DB.3040502@delphij.net> Date: Wed, 27 Feb 2013 16:37:47 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Glen Barber Subject: Re: ZFS problems References: <1953411.keAzGZcpTL@zeus> <46832A2E33D240EABA0FBCF5F9C404C2@multiplay.co.uk> <9083248.zOq17M83H4@zeus> <20130228003346.GE82833@glenbarber.us> In-Reply-To: <20130228003346.GE82833@glenbarber.us> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Martin Matuska X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 00:37:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 02/27/13 16:33, Glen Barber wrote: > Hi Martin, > > On Wed, Feb 27, 2013 at 07:21:39PM -0500, Derrick Dantavious > Edwards wrote: >>>>> [...] I updated sources a couple of days ago and when I >>>>> rebooted to continue to the upgrade process I received >>>>> errors when I attempted to mount zfs filesystem. The error >>>>> looked like this. >>>>> >>>>> zpool mount -a >>>>> >>>>> internal error: Invalid arugment >>> >>> [...] the Kernel and the ZFS tools in userland need to be >>> updated at the same time. >>> >>> Boot back into the old kernel and (cd /usr/src/cddl && make >>> install) to update the tools to a compatible version. >>> > > In mid-February, zpool version was upgraded to include > lz4_compress. My understanding was that changing from the > OpenSolaris ZFS version number scheme (i.e., "v28") to what we have > on -CURRENT (i.e., "5000") was so that we can track crossing the > point of no return with pool version upgrades. > > On my system, vfs.zfs.version.spa has been at 5000 since this > original change. > > Is my understanding incorrect? Or should vfs.zfs.version.spa be > incremented with major, non-backwards-compatible changes? That's incorrect. In theory vfs.zfs.version.spa will never ever change in the future, and all new features will be denoted by feature flags, which is an extensible way of representing features and whether they are compatible with the running system. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJRLqbbAAoJEG80Jeu8UPuzSC0IAKasVsGlPKhjTl7Eu/Ocmdxz ZnWC1hUEt6MJxrLPprRvDBZRMnGMD5YoQ8maMshy27FzxnKXJ3kHpX60gMCkkRFX aRI4cPTHm6w+935KOMjA/Mso7rM8MUmr6b4qhf0Ar/E55sThAvy3BO1R/KVWYRro 4LuwfHGIg6z/vNYo4SDAtw7SOcD43Wk5JTPb1WlAUJOgMiTK+ceFx7mpd5EYCPvb p6DWttzQ5yqxhmCayvBKLjpLBntdD4/88qRuMn5+TQBOZBrGoiK+9GZTwPMVu2U3 MT+hsUJ6uO8oPwKNSz6BgpP9BwyxreWEI/C7Wk0lbZkNeaauiPyN6qUiDD2di9g= =R5LQ -----END PGP SIGNATURE-----