After an update to ZFS 0.8.4-pve now two storage systems with encrypted datasets will not mount child datasets.
ZFS is treating child/sub datasets as directories. Both systems have an 'encrypted_data' dataset with underlying datasets inheriting encryption details.
This happened today as both systems were updated.
The only way Ive managed to mount the child datasets is:
These datasets are empty, excepting other datasets, which should (and did) mount properly before this update.
ZFS is treating child/sub datasets as directories. Both systems have an 'encrypted_data' dataset with underlying datasets inheriting encryption details.
Code:
root@node05:~# zfs load-key -r raid10bak/encrypted_data
Enter passphrase for 'raid10bak/encrypted_data':
1 / 1 key(s) successfully loaded
root@node05:~# zfs mount raid10bak/encrypted_data
cannot mount '/raid10bak/encrypted_data': directory is not empty
This happened today as both systems were updated.
The only way Ive managed to mount the child datasets is:
Code:
root@node05:~# zfs set overlay=on raid10bak
root@node05:~# zfs mount -a
These datasets are empty, excepting other datasets, which should (and did) mount properly before this update.
Code:
root@node05:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
raid10bak 2.21T 8.32T 296G /raid10bak
raid10bak/encrypted_data 1.92T 8.32T 240K /raid10bak/encrypted_data
raid10bak/encrypted_data/pve 1.92T 8.32T 200K /raid10bak/encrypted_data/pve
raid10bak/encrypted_data/pve/backups 1.92T 8.32T 1.92T /raid10bak/encrypted_data/pve/backups