> On Mon, Apr 27, 2015 at 10:07 AM, Adam Steel <adamgsteel@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html