Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Transfer size indication is broken #26
I have invoked buttersink to transfer snapshots from one filesystem to the other as follows:
The current partial output is:
The percentages end up being larger than 100%, so something is wrong somewhere. (The percentages get incremented and go over 100% while progress information is being displayed.)
(I should also point out that buttersink's heuristic do not seem to be performing so well in this case. The snapshots here were created by a crontab, with diff sizes much smaller than the total volume size, so I think the optimal plan would be to transfer the diffs successively. However, buttersink is apparently trying to transfer the delta with a much older state of the data because it already exists on the destination filesystem.)
Yes, the percentages can be arbitrarily larger than 100%. Buttersink used heuristics to guess at the source diff size, and sometimes (often?) this is incorrect. If you are transferring remotely (e.g. over ssh), buttersink will perform a local diff ahead of time, to get a correct size before determining the optimal transfers. If you are transferring locally, it just uses the guesses, since it would take just as long to measure the actual source size as it does to just do the transfer.
One tip: you can force buttersink to do the pre-measuring if you use ssh:/localhost/path as your destination.
Thanks for the explanations! I understand better now, but still I wonder
Regarding the parenthesis at the end of my report, do you have any
On Mon, May 09, 2016 at 11:29:38AM -0700, Ames wrote: