VM Filesystem corrupted after hanging backup

pos-sudo

Member
Jun 13, 2021
71
7
13
Hello,

We've encountered an issue with an VM which has failed to make an backup, since the backup process didn't stop by itself we killed it by use of the process ID. We managed to fix the filesystem corruption on this particular VM but I was wondering why this can happen on the filesystem of the VM. Is this normal behaviour, is there something we can do different in order to prevent this from happening in the future?

Thanks in advanced!
 
The backup process is creating a QEMU-internal snapshot of the device in order to be able to write a more consistent backup. If the backup fails somehow, this snapshot is not released and will eventually yield to the state you described. I also encountered this a few times and sadly I do not have an answer.
 
The backup process is creating a QEMU-internal snapshot of the device in order to be able to write a more consistent backup. If the backup fails somehow, this snapshot is not released and will eventually yield to the state you described. I also encountered this a few times and sadly I do not have an answer.

Thank you for your response. I guess as long as we manage to fix it and if this wouldnt happen often than it is alright ;)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!