Same storage names on different nodes

[Maksimus]

There are 2 nodes on each with 2 physical disks, when adding them to the storage, on the second node it does not allow creating a disk with the same name as on the first node (2storage disk2 name). But at the same time, if the VM is located on different disks on the first node, then during migration we get an error that there is no storage on node 2 with the name disk2.
Tell me how to create storages with the same names or how to migrate a VM hosted on 2 different storages to 2 nodes.

 

[aaron]

Disable the "Add Storage" Checkbox as it is already defined. Then edit that Storage under Datacenter->Storage and either add the node to the node list, or remove the node limits if you have the same storage on all nodes

 

[Maksimus]

Did everything as you suggested. But all the same at migration I receive an error. How to migrate while maintaining the distribution of disks by storage?

 

[aaron]

Did you take a look at the config of the storage under Datacenter->Storage? In the top right corner of the windows when you edit the storage is a list of nodes on which it should be available. Most likely you either need to add the other node, or remove those limits completely.

 

[Maksimus]

Not very obvious. But now everything works. Maybe it's in the manual somewhere and I didn't see it?

 

[johnnyoops]

I have a related question…

If I’m trying to create a storage location called vmdata on each node of my cluster, but it will be a different storage type for different nodes, is that possible? I want to have a zfs pool on balto, and an lvmthin on each of my other cluster members. Right now the zfspool shows up as enabled on balto, and disabled on each of the other cluster members, and there is no lvmthin called vmdata (enabled or disabled) on any of the nodes. Now there could be another issue, which is that on the non-balto nodes, pve / data is already local-lvm, so I’m creating a second name for the same storage location.

A

Here’s the end of my storage.cfg:

# Alias for LVM-thin on non-Balto nodes
lvmthin: vmdata
    thinpool data
    vgname pve
    content images,rootdir
    nodes fluffy,fido,scout

# Alias for ZFS pool on Balto
zfspool: vmdata
    pool containertank
    content images,rootdir
    sparse 1
    nodes balto
root@balto:~#

 

[aaron]

If I’m trying to create a storage location called vmdata on each node of my cluster, but it will be a different storage type for different nodes, is that possible?

That won't work.