Created cluster, one node storage gone

F

FuriousRage

Renowned Member
Oct 17, 2014
130
7
83
Hi.

I have 2 seperate pve's joined them in a cluster.

At first i couldnt because i already had made a vm in the joining one.

So i made a backup of it and removed the vm. then i could join it.

But now, the joining pve vm/iso/etc storage is no more
Screenshot_20260529_204409.png


But if i check /var/lib/vz/dump the backup is there.
Screenshot_20260529_204448.png


lsblk
Screenshot_20260529_204543.png



Also, the btrfs drives on the other pve, cant be used in the pve2 it seems
Screenshot_20260529_204641.pngScreenshot_20260529_204652.png


Any ideas?
 
bbgeek17 said:
What is the context of your /etc/pve/storage.cfg? does it contain "node" restriction by chance?

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



08:45:37 root@pve2 dump → cat /etc/pve/storage.cfg
dir: local
disable
path /var/lib/vz
content iso,vztmpl,backup

btrfs: local-btrfs
path /var/lib/pve/local-btrfs
content backup,rootdir,import,iso,vztmpl,images
nodes pve

btrfs: parvus
path /data/parvus
content backup,rootdir,vztmpl,images
nodes pve

btrfs: magnus
path /data/magnus
content images,rootdir,iso
nodes pve,pve2
 
As you can see from the output you posted (next time you should use CODE tag </>), the storage with question mark (magnus) is allowed to be present on both nodes. However, most likely is not present on node2 - hence the ?.

The "local" dir storage is marked as disabled cluster-wide.

The "local-btrfs" is restricted to node1 only.

etc


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
As you can see from the output you posted (next time you should use CODE tag </>), the storage with question mark (magnus) is allowed to be present on both nodes. However, most likely is not present on node2 - hence the ?.

The "local" dir storage is marked as disabled cluster-wide.

The "local-btrfs" is restricted to node1 only.

etc


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

Yeah, but the local for pve2 isnt available anymore, where as on the pve (one) all its storage is available.

I disabled/set pve1 only for the btrfs storages because it was annoying to see the unavailable one on pve2, since the btrfs storages doesnt seem to work cross pve's, like zfs seems to work (as having a backup storage on another node).

I more want the local storage on pve2 to work, then have the btrfs's work cross-nodes.

if i remove the "disable", does it matter if i put that on the pve1 or pve2? they both seems to share the storage.cfg
 
The storage.cfg is a globally shared file within a cluster. The configuration in this file must be valid for all nodes.

The name of the storage pool is unique cluster-wide.

Code: 
dir: local
    disable
    path /var/lib/vz
    content iso,vztmpl,backup
This ^ must be valid on all nodes if you want "local" to be present on all nodes. If the paths (or other attributes) are different, then you must scope the storage to a particular node , and then create a new pool with a different name for the other node.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
The storage.cfg is a globally shared file within a cluster. The configuration in this file must be valid for all nodes.

The name of the storage pool is unique cluster-wide.

Code: 
dir: local
    disable
    path /var/lib/vz
    content iso,vztmpl,backup
This ^ must be valid on all nodes if you want "local" to be present on all nodes. If the paths (or other attributes) are different, then you must scope the storage to a particular node , and then create a new pool with a different name for the other node.

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

That path (/var/lib/vz) seems to exist on both nodes, different sub-dirs in it thought.
 
bbgeek17 said:
Then it sounds like you dont need to disable it?
The subdirs are created by PVE as needed based on "context" option.

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

I didn't disable that one, afaik, i never edited the storage.cfg, i just connected the two and it was disabled some how.

Do i just need to remove "disable" and the pve will find it, or is there a better command to re-enable it?
 
You must log in or register to reply here.
Top Bottom
Back