Dec
9

Fix GIT Lock after GIT Crash

If you ever see the following message when trying to commit your code to a GIT repository.

If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.

The solution is very easy, just delete the .git/index.lock file
~ rm /yourhomedir/.git/index.lock

Then you need to do a git reset
~ git reset

That should do the trick. Let me know if this worked for you.

Tags: git

Author: Julian Castaneda

Julian Castaneda has written 23 articles for us.

4128 CommentsFix+GIT+Lock+after+GIT+Crash2010-12-09+16%3A04%3A12Julian to “Fix GIT Lock after GIT Crash”

Shreyas February 22, 2011 at 3:02 am

It worked . Thanks a lot!

Reply
- juliancc February 22, 2011 at 8:10 am
  
  Great to hear that this solution worked for you.
  
  Reply
Jon December 14, 2011 at 1:06 am

I am getting the following error while push the commit

git push origin master

fatal: unable to create 'refs/heads/master.lock': File exists fatal:
The remote end hung up unexpectedly

I thought of removing the lock file (refs/heads/master.lock) from my local machine. But this file is not available.

I think this file is in git server.

If i remove this file from server will it solve the issue? ( if the file exists in server)

What is the origin of this issue?

Reply
Malek January 21, 2012 at 9:45 am

Merci beaucoup

Reply
Caedes April 25, 2012 at 9:17 am

Works! Thx!

Reply
Mikael May 22, 2012 at 2:02 pm

Worked for me too. Thanks a lot!

Reply
Mikus June 1, 2012 at 5:20 am

another thankful git user

Reply
@MrSmith9ja July 14, 2012 at 5:04 am

Thanks, worked like a charm.

Reply