Hi,
I’ve been trying to deal with corrupted chunks due to the sftp bug and have noticed that duplicacy check -chunks
with either the -id
or -r
flags still seem to download and check the entire storage repository based on the number of chunks it reports. For example, duplicacy list -tabular
shows that one particular snapshot ID has 18,963 total chunks using up 73gb of space, but duplicacy check -id <snap> -chunks -stats
reports that it’s verifying 81,000 chunks, which would be about the total size of all snapshots in the storage. The same thing happens when I try to check a specific revision with -r
.
Is this a bug or is check -chunks
not supposed to work with these flags? I have quite a lot of data in B2 that I also want to verify but it’s going to be expensive if I have to download the entire bucket to verify only one of the snapshot IDs.
Thanks!