Re: ZFS problems

看板FB_current作者時間12年前 (2013/04/27 13:32), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串12/12 (看更多)
--cz6wLo+OExbGG7q/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 27, 2013 at 04:37:47PM -0800, Xin Li wrote: > > 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. > >=20 > > On my system, vfs.zfs.version.spa has been at 5000 since this > > original change. > >=20 > > Is my understanding incorrect? Or should vfs.zfs.version.spa be=20 > > incremented with major, non-backwards-compatible changes? >=20 > 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. >=20 Thank you for clarifying. As there does not seem to be a specific sysctl that we can look for, I am inclined to say there should be UPDATING entries for such changes to note (at least for now) that 'make -C /usr/src/cddl install' can help prevent foot shooting. Thoughts? Glen --cz6wLo+OExbGG7q/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRLqhUAAoJEFJPDDeguUajAPwH/j3P/pL0RiqmHN31t6aqvN8g O6rEgqHD41z8bFZaBvFax6iKgzMvu2XmhPTaOsxRxDCcRWQOnfE4PLipXdBHe4ri vhvOy9JWtqLOQOSoyXhAAIyoZ72ak3RCHgYrz55oaUo31zXA6WUz8wDgmXzCv2o2 i1GdTDcg7LNtVrxqgspBD/3jDQWhuUiqE43HRIOa+b036naiFfdBgoXG4P9CWaph 9+uXfDhakA4T2e1VOwxpEph4JnBGNpak6TolNk9ctqaIafSp71GuLEzLX53YGYKD eaAf4ghhLp8oQmZWHdjp9C4H6l/vgKQk14SGgf5tG88vmTYvAm0PpwbV/J7Qw20= =Oh+C -----END PGP SIGNATURE----- --cz6wLo+OExbGG7q/--
文章代碼(AID): #1HUsBXSi (FB_current)
文章代碼(AID): #1HUsBXSi (FB_current)