One server is out because of the aforementioned error, another will be out for the duration of the reboot. I will add 2 votes for a node temporarily to make sure quorum is maintained during this time.
Backup job is stuck and I cannot stop it or even kill it
- Thread starter cym
- Start date
-
- Tags
- backup error vzdump hook
Ah okay, I was under the impression that it was a dedicated backup server that had the problem and not a node of the cluster. Yes, this is bad with respect to quorum.
After trying to fix the broken Proxmox node for what felt like an entire day, a simple reboot of my NAS (i.e. the NFS server) fixed the PVE node. The only reason I realised is that even mount -a was timing out. I don't really know what I'd log as a bug, but I feel like a broken storage mount shouldn't necessarily cause an entire PVE node to fall into ??? state. Even the proxmox storage manager command line tool would just hang.
Unfortunately, weird things can happen if you have a hanging NFS share and it is NOT a PVE problem, it's a general Linux problem, don't know about the BSDs, never had such a setup there.
Yes, I meant the server with the hanging process, so one of the "other" nodes.