Brad - ZFS Features and Upgrades

New About Yours API Help
1.8 KB, Plain text
Hello there, Benedict and Allan and JT,

I have a question about ZFS features and versions, and about upgrading pools. With all of the exciting features happening or in the pipeline, I'm curious about a couple of things.

I have zpools on my FreeNAS, on my TrueOS box, on my Trident test laptop, and a couple of external hard drives with zpools that I can mount on my BSD boxes as well as my Linux box running ZFS on Linux. 

So when I do a zpool status on the two pools on my trueos box (one is mirrored SSDs, the other mirrored spinning rust), I see a message: 

status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details.

And sure enough, on both pools, embedded_data, extensible_dataset, hole_birth, and large_blocks are disabled. In addition, sha512 and skein are disabled on the SSD pool.

In addition, every pool I have gives a value of "version   -  default" for zpool get version, and zfs get version reports "version   5    -" for each pool on all platforms. However, I did "zpool get all | grep feature@" and found that different OSes/ZFS versions have different numbers of and different features. The TrueOS box and the FreeNAS box both have 14, the Trident box has 19, and the ZFS on Linux system has 11. So is the warning about zpool upgrade inaccurate?

When I first started using BSD, I spoke to someone in IRC, who, I found out later, worked for iXsystems. He said he never upgraded his pool. What are the best practices for pool upgrades? Should I do an upgrade on the box that says it needs an upgrade?

Pasted 4 months, 2 weeks ago — Expires in 227 days