Did anyone tryed to use zfs encryption? I have installed test environment (zfs raid 10 with 4 HDD), then created encrypted dataset.
zfs create -s -V 104857600k -o encryption=on -o keylocation=prompt -o keyformat=passphrase rpool/data/vm-100-disk-0
Then rebooted server and system wont boot...
But you can simply make zfs clone on this snapshot and then copy data from this clone to new zvol (as you do when we cloning with "current" option). After that - destroy this zfs clone zvol.
Is this a problem?
root@pve:~# zfs clone rpool/vm-123-disk-1@autodaily180531050002...
This issue appears, when destination storage has some load.
As I can see, pvesr makes this steps:
1. Make snapshot on source storage
2. Send it to destination
3. Remove previous snapshot from destination storage - here it got an 10 seconds time out! zfs destroy operation from your storage some...
For me, everything is working fine with this storage config, without ports:
rbd: ceph-rbd
monhost 10.200.0.3;10.200.0.1;10.200.0.2
username admin
content images
pool rbd
When I built this cluster, I have the same problem, but it was my mistake with keyring file...
Just remove this hdd on Hardware tab. Your hdd will remain there as Unconnected. Click on it and connect as IDE.
Or you can manually edit host config file in /etc/pve/qemu-server
May be this is some pmxcfs issue, see syslog messages about corosync and so on. https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs)
Try to enable debugging, if no errors.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.