avoid cleaning up move log when drop from remote fails
move: Improve resuming a move that succeeded in transferring the content, but where dropping failed due to eg a network problem, in cases where numcopies checks prevented the resumed move from dropping the object from the source repository. This was earlier done for moves that got interrupted during the drop stage. Sponsored-by: Svenne Krap on Patreon
This commit is contained in:
parent
13fc6a9b6a
commit
6d0b243d9d
3 changed files with 43 additions and 17 deletions
|
@ -10,3 +10,5 @@ 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]]
|
||||
|
||||
> [[fixed|done]] --[[Joey]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue