Please describe what you are doing to trigger the bug:
Regular nightly backup and prune to B2 storage. I only have 1 snapshot at any given time. Local data is taking to 503GB but chunks show that it’s taking up 834GB.
The commands I run nightly via cron are:
/usr/local/bin/duplicacy backup -stats -limit-rate 3750 -threads 24
/usr/local/bin/duplicacy -v -log prune -keep 0:1 -threads 24
/usr/local/bin/duplicacy check -a -stats
Please describe what you expect to happen (but doesn’t):
Expect chunks to roughly match local data after several prunes.
Please describe what actually happens (the wrong behaviour):
There’s a ~300GB delta where Duplicacy / B2 is using more than what’s on disk.
This is what duplicacy shows:
root@pbs:/mnt/datastore# /usr/local/bin/duplicacy check -a -stats
Storage set to b2://CorsairBackup
download URL is: https://f000.backblazeb2.com
Listing all chunks
1 snapshots and 1 revisions
Total chunk size is 833,925M in 150724 chunks
All chunks referenced by snapshot datastore-backup at revision 32 exist
Snapshot datastore-backup at revision 32: 158666 files (500,088M bytes), 833,925M total chunk bytes, 833,925M unique chunk bytes
Snapshot datastore-backup all revisions: 833,925M total chunk bytes, 833,925M unique chunk bytes
This is what du shows:
root@pbs:/mnt/datastore# du -h -d0