Closed httaotao closed 4 years ago
Why is it a problem? Just use the symbolic link created by ZFS instead of an absolute /dev/zdX
path?
Why is it a problem? Just use the symbolic link created by ZFS instead of an absolute
/dev/zdX
path?
Sorry, I don't know how to use the symbolic link created by ZFS.what's the command like? thanks.
Sorry, I don't know how to use the symbolic link created by ZFS.what's the command like? thanks.
For example, if you need to reference k8s-1m-stg
, use gpool/DATA/glusterfs/k8s-1m-stg
(or /dev/zvol1/gpool/DATA/glusterfs/k8s-1m-stg
depending on what you are doing).
That symbolic link will point at the correct device, regardless of how it is named during boot.
Sorry to disturb, because I encountered an unsolvable problem when using zfs. The name of the block device created by zfs changes after ubuntu18 restart . For example:
when I use the command to create zfs volume:
'gpool/DATA/glusterfs' is a pool path.Then I find out the devices created by zfs,such as
But when I restart the system ubuntu18.04, the devices will change,like that
I don't know why does it happen. I also guess may the Linux kernel problem ,because when I install zfs, it also happened. The content of the configuration file is as follows
Finally, this is the zpool status infomation