From owner-freebsd-current@FreeBSD.ORG Thu Feb 28 00:33:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 30058E73; Thu, 28 Feb 2013 00:33:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id CB723D34; Thu, 28 Feb 2013 00:33:50 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 5006B23F645; Wed, 27 Feb 2013 19:33:48 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.8.0 onyx.glenbarber.us 5006B23F645 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Wed, 27 Feb 2013 19:33:46 -0500 From: Glen Barber To: Martin Matuska Subject: Re: ZFS problems Message-ID: <20130228003346.GE82833@glenbarber.us> References: <1953411.keAzGZcpTL@zeus> <46832A2E33D240EABA0FBCF5F9C404C2@multiplay.co.uk> <9083248.zOq17M83H4@zeus> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="47eKBCiAZYFK5l32" Content-Disposition: inline In-Reply-To: <9083248.zOq17M83H4@zeus> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 28 Feb 2013 00:33:51 -0000 --47eKBCiAZYFK5l32 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 contin= ue to > > >> the upgrade process I received errors when I attempted to mount zfs > > >> filesystem. The error looked like this. > > >>=20 > > >> zpool mount -a > > >>=20 > > >> internal error: Invalid arugment > >=20 > > [...] > > the Kernel and the ZFS tools in userland need to be updated at the same > > time. > >=20 > > Boot back into the old kernel and (cd /usr/src/cddl && make install) > > to update the tools to a compatible version. > >=20 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? Thanks in advance. Glen --47eKBCiAZYFK5l32 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRLqXqAAoJEFJPDDeguUajNF4H/2X6la58Z9858N6yd/B/cwxY ByzGgbyaN8kqvN3XT4MkQRkekM3XyjlKHRa9Pbs9QBt1kQaszTQ9H7soURqflCM+ KrwcX0xRpS8Bm6Xnj8Ma+XnY+IYmPIYKEsYuRoPL6+JisPHWwWAGEaZ2fxai5Jng HBTkWShN1fHensDDNepFf4x72/eYxkJqykkp+gay6LMd3jrXnEd3bEuUKl4j43Mk r6l8Gr+OGIe34l8GmLLpQiGQ2m4eTFDtw5wIvYTstqXuCasqyJzjaff34xu9mSIa 3A9AmfW93I9Q30/+yUhzFA6Fn39PesnrPEPX7bQri4LI3RHMc4Gcmy74cCMW18M= =ZSSX -----END PGP SIGNATURE----- --47eKBCiAZYFK5l32--