You are not logged in.
Recently, I started having a problem with ZFS pools that I did not experience before.
If there is a pool POOL mounted at /mnt/pool and it contains a dataset POOL/dataset, which mounts itself at /mnt/pool/dataset, then any files or folders inside the POOL that are not inside the dataset, will not be visible because ZFS mounts the dataset first, and then the pool itself fails to mount, because the dataset mount caused the fact that there are already folders created inside the /mnt/pool mountpoint.
If I do
zfs umount POOL/dataset
rm -rf /mnt/pool/dataset
zfs mount -a
then it works, but I have to repeat this process after every reboot
Last edited by Lockheed (2017-09-20 21:33:03)
Offline
You could define the parent pool in fstab to make sure it gets mounted early, or reset the child mountpoint to inherit with
# zfs inherit -r mountpoint POOL/dataset
The -r option "[...] clears the current property setting for all descendent datasets."
Last edited by marian (2017-09-21 20:35:34)
Offline