warning: unable to access non-existent chunk

[RolandK]

hello,

i had some problem with a backup disk.

why is this only considered to be worth a warning ?


2025-05-19T07:40:44+02:00: marked 67% (574 of 856 index files)
2025-05-19T07:40:47+02:00: marked 68% (583 of 856 index files)
2025-05-19T07:40:52+02:00: marked 69% (591 of 856 index files)
2025-05-19T07:40:54+02:00: warning: unable to access non-existent chunk 7beedbe842ef534562022be3999aa0b49ccb95392b213d73c7289c31dc03e4b8, required by "/backup/repli_msb_pbsds_pve-sm2/vm/108/2025-03-16T20:03:02Z/drive-scsi0.img.fidx"
2025-05-19T07:41:02+02:00: marked 70% (600 of 856 index files)
2025-05-19T07:41:18+02:00: marked 71% (608 of 856 index files)
2025-05-19T07:41:23+02:00: marked 72% (617 of 856 index files)
2025-05-19T07:41:24+02:00: marked 73% (625 of 856 index files)
2025-05-19T07:41:25+02:00: marked 74% (634 of 856 index files)
2025-05-19T07:41:27+02:00: marked 75% (642 of 856 index files)

 

[Chris]

Hi,
this has been changed with https://bugzilla.proxmox.com/show_bug.cgi?id=2909. As far as I can see the motivation was to distinguish the missing chunks, which the garbage collection will not be able to act on from actual errors of the GC itself. But instead of just escalating the warning to an error, the actually better fix for this will be the proposed marking of backup snapshots referencing the missing chunk, see https://lore.proxmox.com/pbs-devel/1736772071.mcbrxnbmft.astroid@yuna.none/

 

[RolandK]

thanks