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?
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
Kam in meinem Post 'rüber, dass ich gegen Ceph bin? In meiner viel zu kleinen Umgebung hatte ich mich am Ende mangels Ressourcen dagegen entschieden...
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.
dir: local
disable
path /var/lib/vz
content...
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...
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...
Exactly. Separate zpool in the same machine holding the PBS datastore and backups of the PBS LXC.
In case the Proxmox rpool dies:
- reinstall Proxmox,
- restore the last backup of the PBS LXC from the separate zpool in the same machine.
-...
So standard Proxmox backup doesn't do incremental backups and PBS does?
If that is the case PBS in LXC container makes sense for local backups to another zfs pool. But do I really need backups on the same machine where my Proxmox is when I have...
So standard Proxmox backup doesn't do incremental backups and PBS does?
If that is the case PBS in LXC container makes sense for local backups to another zfs pool. But do I really need backups on the same machine where my Proxmox is when I have...
community sub is below basic, but still a valid sub, so all the messages are correct.
you have subs everywhere, just not on a high enough level to be eligible for enterprise support on PDM.
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
Hi,
Well, bad RAM generally produces crash / reboot (application and/or whole unit) / segfault.
An OOM is more when there is not enough RAM and eventually can happen if you use a server with ECC and the server detects the faulty stick and...