Re: Possible race condition with git-rebase + .git/index.lock
- Date: Tue, 12 Mar 2019 12:45:26 -0400
- From: Sergio Durigan Junior <sergiodj@xxxxxxxxxxxx>
- Subject: Re: Possible race condition with git-rebase + .git/index.lock
On Tuesday, March 12 2019, Duy Nguyen wrote:
> On Tue, Mar 12, 2019 at 5:18 AM Sergio Durigan Junior
> <sergiodj@xxxxxxxxxxxx> 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?
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible