Proxmox confused about SAN Storage Capacity

Technolust

New Member
Mar 30, 2023
1
0
0
We built proxmox on Cisco UCS Blades and NetApp Storage. When you attach SAN LUN over Fibre Channel Proxmox will see the LUN and it's capacity. However, when you try to build a VM or container Proxmox shows 0 available storage to build onto. The issue is, Proxmox adds a global filter to the /etc/lvm/lvm.conf file and when you create a LUN and attach it to Proxmox it then creates a preferred_names filter under a different block.

The fix is to edit the /etc/lvm/lvm.conf file under the devices { } section at the end.

This is the original:

Bash:
devices {
 global_filter=["r|/dev/zd.*|","r|/dev/rbd.*|"]
}
devices {
 preferred_names = [ "^/dev/mapper/", "^/dev/sd" ]
 filter = [ "a|/dev/mapper/.*|", "r|/dev/sd.*|" ]
}

This is what it needs to look like:


Bash:
devices {
    # added by pve-manager to avoid scanning ZFS zvols and Ceph rbds
    global_filter = [ "r|/dev/zd.*|", "r|/dev/rbd.*|" ]

    preferred_names = [ "^/dev/mapper/", "^/dev/sd" ]
    filter = [ "a|/dev/mapper/.*|", "r|/dev/sd.*|" ]
}

Just thought I would post this for anyone looking for help and to maybe see if proxmox devs can fix this in an update.
 
Last edited:
Hi @Technolust , welcome to the forum.

Thank you for sharing this interesting observation. However, the default PVE installation does not come with lvm.conf containing two "devices{}" stanzas.
Something happened to your file, most likely human intervention.

LVM does not merge duplicate config entries - the last one wins. So the behavior you saw is expected for a misconfigured system.

Cheers


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox