Please describe the problem.

Ideally annex should detect all "paranormal" cases such as running on NFS mounted partition, but according to Happily ignorant we were running annex (5.20151116-g76139a9) on NFS mounted partition until we filled up 2TB of allocated to us space with .nfs* files. Well -- apparently according to above we should have tried pidlock... trying now but doesn't work :-/

*$> git clone smaug:/tmp/123 123-clone && cd 123-clone && git config annex.pidlock true && echo 124 > 124.dat && git annex add 124.dat && git commit -m 'added 124' && git annex move --to=origin 124.dat
Initialized empty Git repository in /home/yhalchen/123-clone/.git/
remote: Counting objects: 22, done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 22 (delta 3), reused 0 (delta 0)
Receiving objects: 100% (22/22), done.
Resolving deltas: 100% (3/3), done.
total 1
1 123.dat@  1 README.txt
(merging origin/git-annex into git-annex...)
(recording state in git...)
add 124.dat ok
(recording state in git...)
[master 0f1092a] added 124
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 120000 124.dat
move 124.dat (checking origin...) git-annex: content is locked

$> echo $?

BTW running move in our old now somewhat screwed up annex, results in a differently expressed error:

Looks to me like I fixed the reported problem 3 years ago, in 1a8ba7eab4677be18fef5d6e1c2e59607594c446.

That fix was never confirmed to work, but I see no reason why it wouldn't, so if it didn't please reopen. done

(As far as detecting nfs and enabling pidlock, there is --Joey