Search results

configurable in the storage settings, but it will only affect newly allocated volumes What do you mean with that?

But how it can be that Proxmox does not have implemented something that says " can not create VM local-ZFS will be filled up" Do you maybe have some websites where we can see how to set up zvols? BR

Hi all, we face some strange issue with the local-zfs that no warning is set, when the storage gets full. The command zpool list rpool shows the amount of free rpool storage space. Now I created a VM (see attached picture) with a virtual disk which is larger than the remaining rpool storage...

Our Problem ist resolved now. We hat 11 Nodes in 1 Job this was the error. I reduce the nodes to 6 and everything runs perfect errors anymore. This Link https://bugzilla.proxmox.com/show_bug.cgi?id=3086 helps me to understand what is wrong and what I should do. BR, KC IT-Team

After changing to debug level, the log gets flooded with: 1685699121.67057: debug: received EOF 1685699121.167240: debug: received EOF 1685699121.267419: debug: received EOF 1685699121.367583: debug: received EOF 1685699121.467762: debug: received EOF 1685699121.567933: debug: received EOF...

O maybe I unterstand what you mean. Not all of our VM's running at the same time, see timetable when the Backups starts.

No this is not possible we have 350 VM's running on all nodes

Yees all our Backup from all nodes goes on one PBS. The VM's are not on one hypervisor they are distributed. I attached to configs. The VM 295 had the error durrings tonight backup and the 212 not so i put this 2 configs here in. Let me know if you need some more information.

The VM Config's are the same no defference between them. We are using PBS for Storage. Here ist the pveversion: pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.15.74-1-pve) pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a) pve-kernel-5.15: 7.3-3 pve-kernel-5.13: 7.1-9 pve-kernel-5.4...

Hi, they are no errors in the logfile.

Still the same thing, the error come again.

Yes we run the latest PVE version. I stop and start the VM again, now I will wait to see if this helps. I think this will not resolve our problem.

Yes the qemu agent run fine. The strange thing is, that everytime the same Backupjob have this error

Hi, our Backups always get the same error see attached picture. Does anybody have/had the same issue or some ideas what we can do? What I know is that, when i delete the Backup with the error and do it manual it finish in 10 seconds without error? Thank you, KC IT-Team

Thanks for the Help. BR, KC IT - Team

Yes we know that we must have some space left if the node fail. If you take a look to the attached screen you see that ist ~50 tb left space for what is this going?

We have now more, but only 12 TB. The Cluster still show 50 TB free space? BR, KC IT-Team

The cluster is running a while and the nodes are on different versions. Does this can be also the reason?

Yees the recovery is done, he shows now 2048. Attached he commands

so nothing changed, the Storage is still the same, any other Ideas maybe? Should we go back to ZFS If this does not work like It should? BR, KC IT-Team