> Regarding your other issue, it is possible that using /dev/sdX for vdev
> causes it. Depending on the type of block device these names are not
> stable and may change on boot or when udev runs. It's more reliable to
> use /dev/disk/by-uuid or /dev/disk/by-partuuid which are persistent.
I think this is valid for pools (which in fact, I configure with this strategly, specifically by using `/dev/by-id` entries), but not for zvols (which is where I experienced the problem).
Zvols use `/dev/zd*` symlink destinations, and those were the entries that I found swapped.
I don't think there is a any relation between `/dev/disk/by-(id|uuid)` and zvols, since zvols live inside pools.
> Regarding your other issue, it is possible that using /dev/sdX for vdev by-partuuid which are persistent.
> causes it. Depending on the type of block device these names are not
> stable and may change on boot or when udev runs. It's more reliable to
> use /dev/disk/by-uuid or /dev/disk/
I think this is valid for pools (which in fact, I configure with this strategly, specifically by using `/dev/by-id` entries), but not for zvols (which is where I experienced the problem).
Zvols use `/dev/zd*` symlink destinations, and those were the entries that I found swapped.
I don't think there is a any relation between `/dev/disk/ by-(id| uuid)` and zvols, since zvols live inside pools.