Can't retrieve fossil from B2

Support
#1

Hello - prune and check fail on the B2 copy of local storage. Here is a sample log entry:

2023-05-15 20:42:19.069 WARN DOWNLOAD_FOSSIL Chunk 056177f4bf85bdfa7bff515bc48026c81a3be53f02f8af4e6f29a08866255dae is a fossil
2023-05-15 20:51:47.819 ERROR DOWNLOAD_CHUNK Failed to download the chunk 056177f4bf85bdfa7bff515bc48026c81a3be53f02f8af4e6f29a08866255dae: URL request ‘https://f000.backblazeb2.com/file/SPS-Duplicacy-Backup/chunks/05/6177f4bf85bdfa7bff515bc48026c81a3be53f02f8af4e6f29a08866255dae.fsl’ returned 404 File with such name does not exist.
Failed to download the chunk 056177f4bf85bdfa7bff515bc48026c81a3be53f02f8af4e6f29a08866255dae: URL request ‘https://f000.backblazeb2.com/file/SPS-Duplicacy-Backup/chunks/05/6177f4bf85bdfa7bff515bc48026c81a3be53f02f8af4e6f29a08866255dae.fsl’ returned 404 File with such name does not exist.

The chunk exists on B2, but without the fsl extension. There are two versions of the chunk on B2. The most recent is a zero length hidden file (so it has no native or friendly urls). The previous version is non-zero, but has no friendly url (B2 says “new version”). So it is understandable that when duplicacy asks for the chuck with an .fsl extension, the call fails.

The following post may be related.
https://forum.duplicacy.com/t/error-finding-fsl-on-b2/7470

I’m using the web version. CLI is version 3.1.0. What can I do to correct this? If fixing this requires the commit mentioned in the linked post, how can I get the release? I’m not really up to compiling a custom version of the CLI.

Thanks!
Jeff

#2

You can delete the zero length version. That will expose the previous version which can then be downloaded. There won’t be many of these chunks as only meta chunks are affected by this issue.

#3

Thank you. How do I delete it using the B2 web interface? I did not see an option in the B2 file browser to unhide a file or delete a hidden file.

Will there be a new release of Duplicacy that will have this fix in it?

#4

Select the version with zero length, then click the Delete button. This should remove the hidden file.

#5

Sorry for my slow reply …

The first time I tried, the B2 delete button was grayed out, but since then the button has been available. Probably user error. I deleted several fossils as identified by the log and got the backup working again. However, a few weeks later the problem has happened again. I know how to fix it now, but I don’t want to have to manually manage raw files in the cloud storage - if the failure happens often that is a pain and if it happens rarely I am likely to forget the details of how to do it and make a mistake. What can I do to avoid this problem until the committed fix is released? Thanks!

#6

Happened again. @gchen, any update on when the fix for this will be included in a release? Thanks! Jeff

Error finding .fsl on B2
#7

Hey, I just found my wife’s macbook has been doing this for months, sigh!
I tried deleting some of the zero byte files manually from the B2 web interface… but there are hundreds of them, if not thousands. So that’s not possible, for my skillset.
@gchen - We need a fix for this in a release please!
Carl

1 Like