Re: Regular Rebase Failure

From: Adam Steel <adamgsteel@gmail.com>
Date: Apr 29, 2015, 15:22 UTC
Message-ID: <CAF72XQfySo7S7hYwzTeMZQSj5Ko0Czarikd6TbBiJpFPj+aGiQ@mail.gmail.com>
In-Reply-To: <CABURp0rkkpP_EuWA0O=gF=O=pyLGbh0Vzvp+yC-ckpJM4wU0gQ@mail.gmail.com>

Nope, this is local on an OSX system with only one user, no local network. This happens about every third interactive rebase.

On Wed, Apr 29, 2015 at 9:14 AM, Phil Hord <phil.hord@gmail.com> wrote:

Show 29 quoted lines

>> On Mon, Apr 27, 2015 at 10:07 AM, Adam Steel <adamgsteel@gmail.com> wrote:
>>> Stefan,
>>>
>>> So I switched git versions.
>>>
>>> $ git --version
>>> git version 2.3.1
>>>
>>> I'm still getting the same regular rebase failures.
>>>
>>> ---
>>>
>>> fatal: Unable to create
>>> '/Users/asteel/Repositories/rails-teespring/.git/index.lock': File
>>> exists.
>
> Is the repository located on a mounted network share, or could other
> users be accessing it via a network mount?  We had a similar problem
> recently on a new Jenkins VM instance which had only NFS-mounted
> storage available. I don't remember if it was Git that was failing on
> there, and I wasn't directly involved in solving the problem.  But
> while researching the issue I found ominous warnings about the dangers
> of file-locking on remote shares [1]. Which is to say, I don't know
> much, but I heard a rumor...  :-)
>
> Perhaps this is old news and already well covered in Git.  But I am curious...
>
>
> [1] http://0pointer.de/blog/projects/locking.html