Hot answers tagged


You would need to rewrite your data to the expanded zpool in order to rebalance it. Otherwise, as time passes, your writes will be distributed across the entire pool.


There is no reason for the zvol to be stored on the initial devices only. If you enlarge the pool, ZFS will span the updated data on all of the available underlying devices. There is no fixed partitioning with ZFS.


Just now, on ubuntu 16.04 I did sudo find /dev and then created a zvol, and then sudo find /dev again, and then created partitions, and then did a final sudo find /dev to see what was created at each step along the way. What I found was: sudo zfs create -V 8g storage/junkzvol created /dev/zvol/storage/junkzvol sudo fdisk /dev/zvol/storage/junkzvol created /...


VOLSIZE represents that size of the volume as it will be seen by the clients, not the size of the volume as stored on the pool. This difference may come from multiple sources: space required for metadata space required for storing multiple copies (the "copies" parameters) "wasted space" due to padding while aligning blocks of "volblocksize" size to vdev ...


That's normal for ZFS. What's happening is it's coalescing the writes in memory and then committing them to disk at the same time. This a great wiki about what it's doing and how you can tune it:

Only top voted, non community-wiki answers of a minimum length are eligible