[PVE-User] 'asymmetrix storage' and migration...

[Aaron Lauterer]

See inline

On 7/15/21 2:48 PM, Marco Gaiarin wrote:
> 
> I'm a bit puzzled.
> 
> 
> A little 'ZFS' cluster, with two asymmetrical nodes; second node is
> there only, just in case, to run some little VMs (PBX, firewall, ...).
> 
> First node have a second RAIDZ volume called 'rpool-data', that does
> not exist on second node; eg, storage.conf is:
> 
>   dir: local
> 	path /var/lib/vz
> 	content iso,vztmpl,backup
> 
>   zfspool: local-zfs
> 	pool rpool/data
> 	content images,rootdir
> 	sparse 1
> 
>   zfspool: rpool-data
> 	pool rpool-data
> 	content images,rootdir
> 	mountpoint /rpool-data
> 	sparse 1
> 
> Clearly on node 2 'rpool-data' have a question mark.
> 
> 
> I've tried to migrate a VMs from node 2 to 1 that have disks only on 'local-zfs':
> 
>   root at brpve1:~# grep ^scsi /etc/pve/nodes/brpve2/qemu-server/100.conf
>   scsi0: local-zfs:vm-100-disk-0,size=100G
>   scsi1: local-zfs:vm-100-disk-1,backup=0,size=1000G
>   scsi2: local-zfs:vm-100-disk-2,backup=0,size=500G
>   scsihw: virtio-scsi-pci
> 
> but i get:
> 
>   2021-07-15 14:14:54 starting migration of VM 100 to node 'brpve1' (10.15.5.21)
>   zfs error: cannot open 'rpool-data': no such pool
>   zfs error: cannot open 'rpool-data': no such pool
>   2021-07-15 14:14:54 ERROR: Problem found while scanning volumes - could not activate storage 'rpool-data', zfs error: cannot import 'rpool-data': no such pool available
>   2021-07-15 14:14:54 aborting phase 1 - cleanup resources
>   2021-07-15 14:14:54 ERROR: migration aborted (duration 00:00:00): Problem found while scanning volumes - could not activate storage 'rpool-data', zfs error: cannot import 'rpool-data': no such pool available
>   TASK ERROR: migration aborted
> 
> 
> Because in 'rpool-data' currently we have no data, i've simply disabled
> storage 'rpool-data', migrate the machine and then re-enabled back.
> 
> 
> Why migration does not work, even if there's no disks in 'rpool-data'?
> 
> Thre's some way to 'fake' an 'rpool-data' on the second node, only to
> have PVE not to complain?

You can limit storages to certain nodes. To do this via the GUI, edit the storage and in the top right of that dialog, you should be able to select the nodes on which the storage exists. Otherwise you will run into certain problems as Proxmox VE expects the underlying storage to be present on the nodes.

> 
> 
> Thanks.
>