mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

bug report

Browse source
This commit is contained in:
Joey Hess 2022-06-09 13:16:39 -04:00
parent 5b7a5eedb6
commit 2f509e529e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/bugs/move_that_fails_at_drop_stage_does_not_resume_correctly.mdwn Normal file
View file

@ -0,0 +1,12 @@
git-annex move takes care to handle resuming an interrupted move, where the
dest received the object, but the drop did not happen before it was
interrupted.
But, the more common case than being interrupted with ctrl-c or power loss
is the drop failing due to a network issue. In this case, re-running move
does not let the drop succeed in cases where the original move would have
let the drop succeed.
The problem is that logMove runs its cleanup action in this case.
So the move.log gets the record of the move cleaned from it. It seems that
the cleanup action should avoid doing that when the move failed. --[[Joey]]