Uploaded chunk percentage greater than 100%

Support
#1

Noticed a weird thing when my daily Duplicacy backup script was running today: the ‘Uploaded chunk’ message was displaying a percentage over 100%. Perhaps this is not abnormal and I’ve just never noticed it though…

Uploaded chunk 1122 size 10427088, 102KB/s 00:10:27 98.9%
Uploaded chunk 1123 size 7741447, 102KB/s 00:07:00 99.3%
Skip chunk cache to keep connection alive
Skipped chunk 1160 size 1048576, 103KB/s 00:02:48 99.7%
Skipped chunk 1161 size 1572880, 103KB/s 00:02:33 99.7%
Skipped chunk 1162 size 1048576, 103KB/s 00:02:23 99.7%
Skipped chunk 1165 size 6947570, 103KB/s 00:01:17 99.8%
Skipped chunk 1166 size 9343593, 103KB/s n/a 100.0%
Skipped chunk 1167 size 3393193, 103KB/s n/a 100.0%
Skipped chunk 1168 size 5104354, 103KB/s n/a 100.1%
Skipped chunk 1169 size 1352078, 103KB/s n/a 100.1%
Skipped chunk 1170 size 2241489, 103KB/s n/a 100.2%
Skipped chunk 1171 size 2407811, 103KB/s n/a 100.2%

It went up to at least 102%. I’m just curious why this is and if this is normal behavior. Thanks!

#2

I suspect that this is caused by some files changing sizes after the indexing phase. I’ll run some tests to confirm.

#3

Ah, that would totally make sense. The backup took way longer than it usually does because for some reason the backup appeared to have stalled/gotten stuck for several hours uploading 1 chunk (happens to me very rarely… maybe 1 out of every 40-50 backups) so there was a significant amount of time for many files to change during that period. However… now that I think about it, I’m using VSS so any changes to files during the backup shouldn’t actually be backed up, right?

#4

If VSS is enabled, then a more likely cause is some files that are actually larger what they claim. During the indexing phase Duplicacy only looks at the metadata provided by the OS to determine the file sizes, which may not be accurate.

#5

Alright, no problem. I was just curious. As always, thanks for the quick reply!