ALL backups are failing with: unable to create temporary directory '/mnt/pve/backup/dump/vzdump-qemu-146-2020_02_12-02_00_02.tmp' at /usr/share/perl5/PVE/VZDump.pm line 703.
We export ZFS via nfs kernel server, working fine all the time. NFS shares are readonly now.
Latest Update was...
it depends - where is your data stored?
We have similar problems:
We have a 15node cluster using ceph, so it is important to stop all VMs on all hosts, before the storage can be stopped.
Proxmox will shut down all VMs on a single host and then shuts down this host.
So it is possible that...
Thanks for your response,
Yes, agent was missing in VM, but activated in options.
If I disable agent in options, the VM properly shutdown, so I guess it uses ACPI-power signal ONLY with disabled agent.
Didn't know that.
For the record: KVM processes became unresponsive, had to be killed with -9
To ensure a proper shutdown of the proxmox/ceph cluster in case of power
failure I experimented with setting a Timeout for quitting VMs.
I've used 80s, but if the VM hangs, it will be killed after 10minutes instead of 80s.
Where do this timeout of 10Minutes come from?
Any help appreciated...
the answers in this thread leaves me a little bit puzzled.
Could anybody of the Proxmox staff members determine an exact limit of nodes in a cluster.
1. Does corosync have a hardcoded limit of nodes and what is the limit?
2. Does corosync have a theoretical limit because of...