Menu
I am having a constant issue with one of my git repos. I keep getting the following error:
fatal: Unable to create 'v:/path/to/files/.git/index.lock': File exists.
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.
I have tried: rm -f ./.git/index.lock as per another thread on stackoverflow but I get this error each time: rm: cannot unlink `./.git/index.lock': Permission denied
When I close down aptana (I am using git in the terminal) I cannot delete the file still.
Any ideas how to get around this?
Another thing to note is this git repo is very slow when I do occasionally get to commit within it (it allows me every 10 tries or so)
Thanks
469
The index. lock file prevents changes to your local repository from happening from outside of the currently running git process so as to ensure multiple git processes are not altering or changing the same repository internals at the same time.
If you don't have any Git processes running, you can delete the index. lock file and try the Git operation again.
Git index is a binary file (generally kept in . git/index ) containing a sorted list of path names, each with permissions and the SHA1 of a blob object; git ls-files can show you the contents of the index. Please note that words index , stage , and cache are the same thing in Git: they are used interchangeably.
Sudo the command:
sudo rm -f ./.git/index.lock
Both errors suggest index.lock is owned by another user. Run the rm as a superuser, then try your commands again. You might also consider setting core.sharedRepository to true if that is, in fact, the case with your repo:
core.sharedRepository
When group (or true), the repository is made shareable between several users in a group (making sure all the files and objects are group-writable).
When all (or world or everybody), the repository will be readable by all users, additionally to being group-shareable. When umask (or false), git will use permissions reported by umask(2). When 0xxx, where 0xxx is an octal number, files in the repository will have this mode value. 0xxx will override user's umask value (whereas the other options will only override requested parts of the user's umask value). Examples: 0660 will make the repo read/write-able for the owner and group, but inaccessible to others (equivalent to group unless umask is e.g. 0022). 0640 is a repository that is group-readable but not group-writable.
See git-init(1).
False by default.
192
The issue ended up being Aptana, everytime I ran this it would cause this error when I tried to commit in git.
I stopped using aptana studio and I don't have this issue anymore.
45
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
