From 85651be9c41c24dcfdd19ae188b1c96d7c51d087 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 7 Dec 2018 17:08:25 +0000 Subject: [PATCH] added bug report about git index lock being held during concurrent operations --- doc/bugs/git_index_lock_.mdwn | 52 +++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 doc/bugs/git_index_lock_.mdwn diff --git a/doc/bugs/git_index_lock_.mdwn b/doc/bugs/git_index_lock_.mdwn new file mode 100644 index 0000000000..5ebe3cd6fa --- /dev/null +++ b/doc/bugs/git_index_lock_.mdwn @@ -0,0 +1,52 @@ +### Please describe the problem. +Concurrent operations fail due to .git/index.lock being held. + +### What steps will reproduce the problem? +git annex fromkey , under high concurrency . Maybe more retries could be added, before failing? + +### What version of git-annex are you using? On what operating system? +(master_env_py27_v28) [11:57 AM /data/ilya-work]$ git annex version +git-annex version: 7.20181031-g43f0718 +build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify TorrentParser MagicMime Feeds Testsuite +dependency versions: aws-0.17.1 bloomfilter-2.0.1.0 cryptonite-0.23 DAV-1.3.1 feed-0.3.12.0 ghc-8.0.2 http-client-0.5.7.0 persistent-s\ +qlite-2.6.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.4.5 +key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_2\ +24 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE\ +2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256\ + BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL +remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external +operating system: linux x86_64 +supported repository versions: 5 7 +upgrade supported from repository versions: 0 1 2 3 4 5 6 +local repository version: 5 +(master_env_py27_v28) [12:00 PM /data/ilya-work]$ uname -a +Linux ip-172-31-80-119 4.14.77-70.82.amzn1.x86_64 #1 SMP Mon Dec 3 20:01:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux +(master_env_py27_v28) [12:00 PM /data/ilya-work]$ +- + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + +2018-12-06 01:22:20,410 - workflow_utils:183:_run - INFO - running command: git annex fromkey --force MD5E-s19330--3541df84bcd805aa205\ +f9ffdca6cc21a.fasta pipelines/dxfailed/analysis-FKPG5480Z3yz3yG21G7F47z1/files/originalInput/stage-4.reference_genome_fasta/0/ref-ebov\ +-makona_C15.fasta cwd=/data/ilya-work +fatal: Unable to create '/data/ilya-work/.git/index.lock': File exists. + +Another git process seems to be running in this repository, e.g. +an editor opened by 'git commit'. Please make sure all processes +are terminated then try again. If it still fails, a git process +may have crashed in this repository earlier: +remove the file manually to continue. +git-annex: user error (xargs ["-0","git","--git-dir=.git","--work-tree=.","--literal-pathspecs","add","--"] exited 123) +T + + +# End of transcript or log. +"""]] + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +It's become an indispensable tool. E.g. I just used it to moved data from more-expensive to less-expensive storage, without needing to worry about getting it back when needed; this frees up not just disk space but mental space :)