Warning Message size

Support
1

I have started getting this warning. I have clicked repaired the database. I then clicked recreate. I then
verified files. I get the below warining for 6 files. Looks like the backup runs fine and shows changes.

Can I fix this?

2021-11-19 19:35:50 -05 - [Warning-Duplicati.Library.Main.Operation.FilelistProcessor-MissingRemoteHash]: remote file duplicati-b748ea9684d174b32b3725dab878ce1be.dblock.zip.aes is listed as Verified with size 36700160 but should be 52428509, please verify the sha256 hash “JXv6WFkHGtb0wHrIzFXvK7t1rtOjvwsrGr7a4+kzSkQ=”

2

Welcome to the forum @randall.reynolds

What storage type is this, and can you access the files? If so, does the size really seem incorrect?

FWIW 36700160 is 0x2300000 in hexadecimal, and such even values are common on file damage.

Sort of, but if a dblock file is damaged, the backup copies of its files are damaged, and are purged.

First, do all known damaged files have dblock in their name, or do you have dindex or dlist files?

3

Its a local Nas with NTFS. I can access the files. All six warnings are dblock files

2021-11-19 19:35:50 -05 - [Warning-Duplicati.Library.Main.Operation.FilelistProcessor-MissingRemoteHash]: remote file duplicati-b748ea9684d174b32b3725dab878ce1be.dblock.zip.aes is listed as Verified with size 36700160 but should be 52428509, please verify the sha256 hash “JXv6WFkHGtb0wHrIzFXvK7t1rtOjvwsrGr7a4+kzSkQ=”

Properties shows 35.0 MB (36,700,160 bytes)

4

What are the other wrong and right file sizes? Can you post or convert to hex with Windows calculator?
Possibly they were all truncations at the end, but that wouldn’t be knowable without taking a closer look.
Looking directly on the NAS might also be worthwhile. There have been cases of consistent wrong size depending on what tool is asking. SMB to NAS has been a problem sometimes, for unknown reasons…

If problem keeps happening, you might see if there is another Storage Type you can use instead of File.

Recovering by purging files is probably the best next path to go down, assuming you want minimal loss.
Although it’s not said, this method seems to need bad dblock files completely gone, not just wrong-size.
Instead of just deleting them, you could move damaged files to some folder outside of the backup folder.

list-broken-files is a commandline tool to say what source files are affected. purge-broken-files can then remove their damaged backups from the backup. Assuming you use the GUI, GUI Commandline may be simplest way to do this. The Target URL and database path are already there. You’ll need to at least pick Command from dropdown, and clear the source paths from Commandline arguments before running it.