Re: ZFS problems
--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--
討論串 (同標題文章)
完整討論串 (本文為第 12 之 12 篇)：