Verify failed with "no such file or directory" but file exists

[bcrespo]

Hello,

I have a job wich failed to verify with this error:

2025-04-19T12:53:20+02:00: check drive-scsi0.img.fidx
2025-04-19T13:42:32+02:00: can't verify chunk, load failed - store 'Syno196', unable to load chunk '3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9' - No such file or directory (os error 2)

But if I look in the datastore, the file exists:

root@pbs:/mnt/syno196# ls -l .chunks/3df3/3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9
-rw-r--r-- 1 backup backup 712129 Apr 19 13:53 .chunks/3df3/3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9
root@pbs:/mnt/syno196#

And if I try to recover the backup with proxmox-backup-debug tool it finish without error:

root@pbs:/mnt/syno196# proxmox-backup-debug recover index vm/106/2025-04-18T19\:04\:29Z/drive-scsi0.img.fidx .chunks --output-path - > /dev/null
root@pbs:/mnt/syno196#

Somebody could help me to figure out the problem?

Bruno

 

[Chris]

Hello,

I have a job wich failed to verify with this error:

2025-04-19T12:53:20+02:00: check drive-scsi0.img.fidx
2025-04-19T13:42:32+02:00: can't verify chunk, load failed - store 'Syno196', unable to load chunk '3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9' - No such file or directory (os error 2)

Is this reproducible, do you get the same error on the same file if you run verification again?

But if I look in the datastore, the file exists:

root@pbs:/mnt/syno196# ls -l .chunks/3df3/3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9
-rw-r--r-- 1 backup backup 712129 Apr 19 13:53 .chunks/3df3/3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9
root@pbs:/mnt/syno196#

If there has been a backup job since, this chunk might have been re-inserted by that backup run, which would have 'healed' also the snapshot previously failing verification.

And if I try to recover the backup with proxmox-backup-debug tool it finish without error:

root@pbs:/mnt/syno196# proxmox-backup-debug recover index vm/106/2025-04-18T19\:04\:29Z/drive-scsi0.img.fidx .chunks --output-path - > /dev/null
root@pbs:/mnt/syno196#

Somebody could help me to figure out the problem?

Yes, as mentioned it could be that the chunk has been re-inserted since. Please also post your proxmox-backup-manager version --verbose and the output of stat .chunks/3df3/3df38d3f4791b98b17d10299b6eb7061e981de8002a3c394c656f661457680c9 executed from your datastores base folder.