diff options
| author |  https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 <https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4@web> | 2016-03-01 00:33:44 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-03-01 00:33:44 +0000 |
| commit | d74b0f1e872bf9f00efb2f707c8cf549e57e59e3 (patch) | |
| tree | e8910c8f7456bdf2db16b45639d6c2856cc2dc00 | |
| parent | 7df0aa01b24b76b84cfdb4320e2931e46b71d742 (diff) | |
initial whining
| -rw-r--r-- | doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock.mdwn | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock.mdwn b/doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock.mdwn new file mode 100644 index 000000000..d3d75e8c8 --- /dev/null +++ b/doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock.mdwn @@ -0,0 +1,31 @@ +### Please describe the problem. + +Ideally annex should detect all "paranormal" cases such as running on NFS mounted partition, but according to [https://git-annex.branchable.com/bugs/huge_multiple_copies_of___39__.nfs__42____39___and___39__.panfs__42____39___being_created/](https://git-annex.branchable.com/bugs/huge_multiple_copies_of___39__.nfs__42____39___and___39__.panfs__42____39___being_created/). 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 :-/ + +[[!format sh """ +*$> 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 $? +1 + +"""]] + +BTW running move in our old now somewhat screwed up annex, results in a differently expressed error: [http://www.onerussian.com/tmp/2016-02-29.png](http://www.onerussian.com/tmp/2016-02-29.png) + +[[!meta author=yoh]] |