Hi,
Got a failed backup job yesterday:
Thats my Debian 11.3 based Zabbix LXC stored on a LVM-Thin storage.
Do I understand it right that the LXC couldn't be backed up because a fstrim was still running?
My backup jobs start daily at 05:30 and I also run a "pct fstrim" hourly via cron (
So i guess "pct fstrim" was started at 06:00:00 and backup was tried 2 seconds later with fstrim still running.
Is there a way to tell PVE to wait for the LXC or retry to backup it later? Or is my only option to edit the cronjob so it won't run in the hours a backup could be running (like
Got a failed backup job yesterday:
Code:
136: 2022-07-10 06:00:02 ERROR: Backup of VM 136 failed - CT is locked (fstrim)Thats my Debian 11.3 based Zabbix LXC stored on a LVM-Thin storage.
Do I understand it right that the LXC couldn't be backed up because a fstrim was still running?
My backup jobs start daily at 05:30 and I also run a "pct fstrim" hourly via cron (
0 * * * * /sbin/pct fstrim 136).So i guess "pct fstrim" was started at 06:00:00 and backup was tried 2 seconds later with fstrim still running.
Is there a way to tell PVE to wait for the LXC or retry to backup it later? Or is my only option to edit the cronjob so it won't run in the hours a backup could be running (like
0 0-5,7-23 * * * /sbin/pct fstrim 136)?
Last edited:
