Hi!
A file is present in my local repository (v7), and in a special encrypted repository using S3. Numcopies is set to 1. Whenever I try to drop the file, git-annex says it's "Unable to lock down 1 copy of file that is required to safely drop it" after having been "checking repository-s3... (unsafe)".
What does "unsafe" means? When I fsck the file in repository-s3, everything's fine and the file is present.
Hmm, that's a surprising error message to see in this situation.
It sort of looks like git-annex has been unable to lock the local copy of the content to indicate that it's in the process of dropping it. I can reproduce the error message if I purposefully make it not provide a content removal lock. But, I cannot find a code path where a content removal lock is not actually provided when dropping from the local repo. (
Command.Drop.performLocalalways passesJust contentlocktodoDrop.)Can you paste a full transcript of this happening so I can be sure I understand what you're doing and seeing?