From: Phillip Wood <firstname.lastname@example.org>
To: Sergio Durigan Junior <email@example.com>,
Elijah Newren <firstname.lastname@example.org>
Cc: Duy Nguyen <email@example.com>, Git Mailing List <firstname.lastname@example.org>
Subject: Re: Possible race condition with git-rebase + .git/index.lock
Date: Wed, 13 Mar 2019 20:40:32 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
On 12/03/2019 19:32, Sergio Durigan Junior wrote:
> On Tuesday, March 12 2019, Elijah Newren wrote:
>> On Tue, Mar 12, 2019 at 9:48 AM Sergio Durigan Junior
>> <firstname.lastname@example.org> wrote:
>>> On Tuesday, March 12 2019, Duy Nguyen wrote:
>>>> On Tue, Mar 12, 2019 at 5:18 AM Sergio Durigan Junior
>>>> <email@example.com> wrote:
>>>>> This works without problems most of the time (well, usually there are
>>>>> conflicts and all, but that's a burden I have to carry). However,
>>>>> sometimes I notice that git fails with:
>>>>> # git rebase origin/master
>>>>> Applying: commitX
>>>>> Applying: commitY
>>>>> Applying: commitZ
>>>>> fatal: Unable to create '/home/xyz/dir1/dir2/.git/index.lock': File exists.
>>>>> The first thing I did was to check whether the index.lock file existed,
>>>>> but it doesn't.
>>>> Is the output this clean? What I'm looking for is signs of automatic
>>>> garbage collection kicking in the middle of the rebase. Something like
>>>> "Auto packing the repository blah blah for optimum performance".
>>> Yeah, this is the exact output. I also thought about "git gc", but I
>>> don't see any output related to it. Is it possible that it's being
>>> executed in the background and not printing anything?
>> Any chance you have a cronjob or other task execution mechanism that
>> is running git commands in various directories (even simple commands
>> like 'git status' since it's not read-only contrary to what some
>> expect, or 'git fetch' which might trigger a background gc)?
> Nope, nothing like this. AFAIK, nothing is touching that repository at
> the same time that I am. Besides, even if I wait some minutes before
> trying again, the bug manifests again.
Do you have any of the files in the repository open in an editor or ide
while you are rebasing? I have seen this message when rebasing and one
of the files is open in emacs which runs git status when it sees a file
has changed which locks the index while the rebase is running.
next prev parent reply other threads:[~2019-03-13 20:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 21:38 Possible race condition with git-rebase + .git/index.lock Sergio Durigan Junior
2019-03-11 22:50 ` Eric Sunshine
2019-03-11 22:53 ` Sergio Durigan Junior
2019-03-12 10:28 ` Duy Nguyen
2019-03-12 16:45 ` Sergio Durigan Junior
2019-03-12 19:23 ` Elijah Newren
2019-03-12 19:32 ` Sergio Durigan Junior
2019-03-12 19:39 ` Elijah Newren
2019-03-12 19:58 ` Sergio Durigan Junior
2019-03-13 20:40 ` Phillip Wood [this message]
2019-03-13 20:48 ` Sergio Durigan Junior
2019-03-13 20:59 ` Jeff King
2019-03-13 21:07 ` Sergio Durigan Junior
2022-10-28 16:04 ` Possible race condition with git-rebase + .git/index.lock - probably a gettext issue Mingun
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).