[SOLVED] garbage collection spam logs by repeatedly failing due to running backup


Active Member
Dec 8, 2008
There is a backup taking 12h+, which is okay. GC is daily.

Now, GC isn't happy when trying to clean up files of an active backup:

2020-08-23T18:34:00+02:00: starting garbage collection on store pub
2020-08-23T18:34:00+02:00: task triggered by schedule 'daily'
2020-08-23T18:34:00+02:00: Start GC phase1 (mark used chunks)
2020-08-23T18:34:06+02:00: TASK ERROR: unable to access chunk fa39eafd5ae27f5fec4caf87bd18b37fdd0825e39a10557d5dbe5ef874ed66f5, required by "/mnt/datastore/pub/ct/999/2020-08-19T02:31:19Z/root.pxar.didx" - update atime failed for chunk "/mnt/datastore/pub/.chunks/fa39/fa39eafd5ae27f5fec4caf87bd18b37fdd0825e39a10557d5dbe5ef874ed66f5" - ENOENT: No such file or directory

And this is repeated every minute, for 10+ hours. Also, UI cannot filter messages by message content, or backup name (eg "ct/999"), so searching requires fiddling in /var/log/proxmox-backup/tasks/.../

Probably not intended as such.


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 your own in 60 seconds.

Buy now!