Adding storage when underlying type is different

D

davemcl

Member
Sep 24, 2022
136
14
23
I have a 3 node cluster all using LVMThin (PERC raid) where the storage pool name is the same for all nodes. Works great.
I want to add a 4th node that is NVMe/ZFS based and use the same storage name for migration purposes - is this possible?

In storage.cfg can I have:
Code: 
lvmthin: SSD-R10
        thinpool SSD-RAID10
        vgname SSD-RAID10
        content images,rootdir
        nodes pve03,pve02,pve01

zfspool: SSD-R10
        pool SSD-R10
        content images,rootdir
        mountpoint /SSD-R10
        nodes pve04
        sparse 0

Trying to do this via the GUI throws an "id already exists error"
Is there a work around for this so migrations still work?
 
(Live): Migration is independent of pool name, only for zfs replication you need to have the same pool names.

Edit: only Live Migration, it seems.
 
Last edited:
no, this is not possible. the workaround for migrations is to set the targetstorage for the migration task. note that not all combinations of source nad target storage type and migration mode will work, especially when snapshots are involved.
 
If the VM is running I can select the target storage otherwise when off I get the above error.

Might have to go MDADM and LVM in this case then... thanks for clarification.
 
You must log in or register to reply here.
Top Bottom