From ebdb17cda735b509f27dd6f807bee51ca3fb2bd5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 28 Aug 2018 12:21:23 -0400 Subject: [PATCH] followup --- doc/bugs/jobs.mdwn | 2 +- ...t_1_2f37448b1ab618cf485d5335d3b2977d._comment | 16 ++++++++++++++++ 2 files changed, 17 insertions(+), 1 deletion(-) create mode 100644 doc/bugs/jobs/comment_1_2f37448b1ab618cf485d5335d3b2977d._comment diff --git a/doc/bugs/jobs.mdwn b/doc/bugs/jobs.mdwn index efd32d76d6..49763134f2 100644 --- a/doc/bugs/jobs.mdwn +++ b/doc/bugs/jobs.mdwn @@ -78,4 +78,4 @@ operating system: linux x86_64 ### 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) - +[[!meta title="v6 git annex add -J crash due to index somehow getting locked"]] diff --git a/doc/bugs/jobs/comment_1_2f37448b1ab618cf485d5335d3b2977d._comment b/doc/bugs/jobs/comment_1_2f37448b1ab618cf485d5335d3b2977d._comment new file mode 100644 index 0000000000..11175b2ecd --- /dev/null +++ b/doc/bugs/jobs/comment_1_2f37448b1ab618cf485d5335d3b2977d._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-08-28T16:16:03Z" + content=""" +Does the .git/index.lock file still exist now that git-annex has exited? + +Can you provide a log with --debug of the git-annex add command? +Can trim it to only the lines containing xargs. + +I am pretty sure git-annex only runs one git add at a time, no matter how +many jobs you configure. It seems quite likely that some other git command +was operating in the repository at the same time and locked the index, +or like the error message says, git may have somehow crashed and left +the index.lock behind. +"""]]