blocks|key|436048|text|除非您真的打算让root拥有您的存储库，否则这听起来像是您意外地以root身份运行了一个Git命令(甚至可能是最初的clone/init)。如果您打算这样做，那么您将不得不以root身份运行存储库中的所有Git命令。如果没有，请运行sudo+chown+your-user[:your-group]+-R+.git来取得它的所有权，然后看看它是否正常工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|436049|entityMap^0|38|15|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Unless you actually intended for root to own your repo, this sounds like you accidentally ran a Git command as root (maybe even the initial clone/init). If you meant to do that, then you'll have to live with running all Git commands in the repo as root. If you didn't, run <code>sudo chown your-user[:your-group] -R .git</code> to take ownership of it, and then see if things work.

blocks|key|650517|text|刚出了点问题...这是Gitbox的错。因此，也许您正在运行的GUI导致了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|650518|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just had this issue... Gitbox was at fault. So maybe you had a GUI running that was causing problems.

blocks|key|650601|text|这可能是一个古老的回答，但我希望这对下一个需要这个解决方案的人更有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|650602|在linux/unix/gitbash/cygwin上，尝试|650603|rm+-f+.git/index.lock|offset|length|style|CODE|650604|在Windows命令提示符下，尝试：|650605|del+.git\index.lock|650606|entityMap^0|0|0|0|L|0|0|0|J|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

This may be an old reply but I'm hoping this is more useful on next who need this solution.

On linux/unix/gitbash/cygwin, try

<code>rm -f .git/index.lock</code>

On Windows Command Prompt, try:

<code>del .git\index.lock</code>

blocks|key|650655|text|有时，Git会在您进行任何更改时，或者很可能是在使用子模块时，创建一个与您的存储库关联的锁定文件。错误消息将向您显示锁文件的路径。Fix:只需手动转到终端中的路径，并通过$+rm+index.lock删除锁定文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|650656|这应该会有帮助。|650657|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Sometimes Git creates a lock file associated with your repo while you are making any changes or most probably when you are using sub modules. 
The error message will show you the path of the lock file.
Fix: Just manually go to the path in terminal and delete the lock file by 
$ rm index.lock

It should help.

blocks|key|436306|text|我遇到了完全相同的错误，但问题不是锁文件。相反，问题是我将另一个git代码库的内容复制到了这个代码库中，包括.git不可见文件夹。因此，SourceTree对我想要将文件暂存到哪个存储库感到困惑(+SourceTree认为我所在的存储库与我的嵌入式.git目录的内容告诉我应该在其中的存储库之间存在不匹配)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436307|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this exact same error, but the issue was not the lock file. Instead the issue was that I had copied the contents of another git repo into this repo, including the .git invisible folder. So, SourceTree was confused about which repo I wanted to stage files to (there being a mismatch between the repo SourceTree thought I was in, and the one that the contents of my embedded .git dir said I should be in).

blocks|key|436339|text|我在Windows上用TortoiseGit和Cygwin遇到了这个问题。我无法删除remove+./.git/index.lock即使具有管理权限，我也尝试了Cygwin和命令提示符，它显示该文件正被另一个进程使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436340|我发现我有两个TortoiseProc.exe实例在运行。我杀死了其中的一个，并关闭了我所有的windows资源管理器窗口，然后就可以删除这个文件了。我不知道解决方案是杀死TortoiseProc.exe的实例还是关闭windows资源管理器窗口。|436341|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this problem with TortoiseGit with Cygwin on Windows. I wasn't able to delete remove ./.git/index.lock even with administrative privileges, I tried both Cygwin and command prompt, it said the file was in use by another process. 

I found that I had 2 instances of TortoiseProc.exe running. I killed one of them, and closed all of my windows explorer windows, and then was able to delete the file. I don't know if killing an instance of TortoiseProc.exe was the solution or closing windows explorer windows.

blocks|key|650789|text|我的解决方案是删除.index文件，并允许Git重新构建另一个文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|650790|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The solution for me was to delete the .index file and allow Git to rebuild another.

blocks|key|436447|text|获取错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436448|Using+index+info+to+reconstruct+a+base+tree...
Falling+back+to+patching+base+and+3-way+merge...
fatal:+Unable+to+create+'/home/user/project/.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.|code-block|syntax|javascript|436449|但是我找不到(也没有删除)那个.git/index.lock文件。|436450|在我的例子中，git-cola正在运行！|436451|显然，它每隔一段时间就会创建.git/index.lock，或者是由于我在命令行上执行的rebase操作导致的--所以git-cola显然会“干扰”Git的命令行运行(或某些Git+CLI操作)。|436452|这可以通过在命令行git+rebase期间关闭git-cola来解决。|436453|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Getting the error:

<pre><code>Using index info to reconstruct a base tree...
Falling back to patching base and 3-way merge...
fatal: Unable to create '/home/user/project/.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.
</code></pre>

But I couldn't find (nor delete) that .git/index.lock file.

In my case, git-cola was running!

It obviously creates that .git/index.lock every once in a while, or caused by the rebase I was doing on the command line and during which I received that error - so git-cola obviously "disturbs" the command line run of Git (or some Git CLI operations).

This is solved by closing git-cola during a command line git rebase.

blocks|key|436493|text|我没有要删除的inex.lock文件，但对我有效的是从文件夹属性对话框的属性窗口中删除只读检查。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436494|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I didn't have an inex.lock file to delete, but what worked for me was removing the Read-Only check from the Attributes window of the folder Properties dialog.

blocks|key|436520|text|我创建了一个空的index.lock文件，使用windows命令将其删除|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436521|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I created an empty index.lock file, deleted it using windows command

blocks|key|650972|text|如果您正在使用GIT+BASH+For+Windows+:-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|650973|运行这两个命令1.+cd+.git+2.+rm+index.lock|650974|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you are using GIT BASH For Windows :-

Run these two commands
1. cd .git
2. rm index.lock

blocks|key|651032|text|当你从中间的原点取消拉取时，就会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|651033|因此，您可以手动从.git目录中删除index.lock文件。|651034|rm+-f+./.git/index.lock|code-block|syntax|javascript|651035|cd进入您的项目目录，然后运行此命令。|651036|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This is happening when you are do cancel pulling from origin in the middle.

so what you can do is manually delete index.lock file from your .git directory.

<pre><code>rm -f ./.git/index.lock
</code></pre>

cd into you project directory and run this command.

blocks|key|651096|text|有时，当安装了多个Git客户端时，另一个Git客户端可能会干扰。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|651097|即。使用任务管理器或Get-Process确保来自TortoiseGit的TGitCache在后台未处于活动状态。|offset|length|style|CODE|651098|entityMap^0|0|A|B|11|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

Sometimes another Git client may interfere when there are multiple installed. 

Ie. make sure with the Task Manager or <code>Get-Process</code> that <code>TGitCache</code> from TortoiseGit is not active in the background.

blocks|key|436799|text|在我的sourceTree应用程序中，我不能执行提交或切换到任何其他提交/分支。时间显示错误，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436800|致命:无法创建blah+blah+blah..|436801|我只是通过goto+.git文件夹(在项目资源管理器目录中)来解决这个问题。并删除索引-文件类型:+LOCK+file.Now+I+get+back+all+access+in+sourceTree..|436802|请确保索引锁定文件..假设你没有得到文件类型，在计算机中改变文件视图设置。注意：.git文件夹通常是隐藏类型的文件夹。|436803|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

In my sourceTree application i am not able to do commit or switch to any other commit/brach. That time shows error like 

fatal: Unable to create blah blah blah..

I simply resolve this by goto .git folder(in project Explorer Dir). And delete the Index ----- [file type: LOCK file].Now i get back all access in sourceTree.. 

please make sure Index lock file.. suppose you dont get file type, change fileview settings in computer. Note: .git folder is normally hidden type of folder.

blocks|key|651220|text|当双击SourceTree切换分支时，我遇到了这个问题。这个问题并不常见，而且是Atlassian+knows+about+it，但他们决定不去解决它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|651221|幸运的是，有一个解决方案。不用双击你想要切换的分支，只需右键单击并选择"Checkout+branch+name“即可。它现在应该成功了。|651222|entityMap|0|LINK|mutability|MUTABLE|url|https://jira.atlassian.com/browse/SRCTREEWIN-1130^0|14|O|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I had this problem with SourceTree when switching branch by double-click on it. The problem is not very common and <a href="https://jira.atlassian.com/browse/SRCTREEWIN-1130" rel="nofollow">Atlassian knows about it</a> but they decided not to fix it. 

Fortunately, there is a solution. Instead of double-clicking on branch you want to switch, just right click and choose "Checkout [branch name]". It should succeed now.

blocks|key|436939|text|最近我也遇到了同样的问题。如果你要检查整个错误消息，它还表明有一些进程正在使用git进程，阻止你删除index.lock。您可以打开IDE，如Visual+Studio或集成了git的相关软件。关闭它并尝试重新存储您的文件。希望能有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436940|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue recently. If you will check the whole error message it also says that there are some process that are using the git process that blocks you from deleting index.lock. You may have IDE open like Visual Studio or related software that git is integrated into. Close it and try re-stashing your file. Hope it helps.

blocks|key|436962|text|它给我带来的好处是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|436963|git+rebase+--abort并重启rebase。|offset|length|style|CODE|436964|正如Andrew提到的，当这种情况发生时，我也在使用PHPStorm。不过，我不需要关闭它。|436965|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9282632/git-index-lock-file-exists-when-i-try-to-commit-but-cannot-delete-the-file#comment65921846_11466435^0|0|0|I|0|2|6|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

What did it for me was:

<code>git rebase --abort</code> and restart the rebase.

As <a href="https://stackoverflow.com/questions/9282632/git-index-lock-file-exists-when-i-try-to-commit-but-cannot-delete-the-file#comment65921846_11466435">Andrew</a> mentioned I was also using PHPStorm when this happened. Didn't have to close it though.

blocks|key|437010|text|del+.git\index.lock为我工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|437011|当我从主分支中签出一个新分支时，我就遇到了这个问题。|437012|在删除index.lock文件后，很容易发生检出。|437013|entityMap^0|0|J|0|0|3|A|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

<code>del .git\index.lock</code> worked for me. 

I was facing this issue while checkout a new branch from master branch. 

Checkout easily happened after deleting the <code>index.lock</code> file.

blocks|key|437060|text|试一试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|437061|rm+-f+./.git/index.lock|code-block|syntax|javascript|437062|如果您没有运行其他git进程，那么只需删除相应项目的index.lock文件即可。|437063|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

try

<pre><code>rm -f ./.git/index.lock
</code></pre>

if you have no other git process running, then just delete the index.lock file of the respective project.

blocks|key|437131|text|首先，您必须导航到项目的特定文件夹。例如，如果您的项目名称是Firstproject，则首先转到项目的目录。然后输入cd+.git，然后导航到git文件夹，输入del+index.lock，删除文件后，index.lock..You将能够像以前一样提交和推送|type|unstyled|depth|inlineStyleRanges|entityRanges|data|437132|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

First you have to navigate to the specific folder of your project..
Like if your project name is Firstproject then first go to the directory of the project..
then type cd .git
then after navigating to the git folder type del index.lock
After the deletion of the file index.lock..You will be able to commit and push as before

blocks|key|437191|text|在我的例子中，没有要删除的index.lock文件。我试图提交109个文件后，用漂亮的格式化。提交更少的文件是最终“解决”问题的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|437192|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case there was no index.lock file to delete. I was trying to commit 109 files after formatting with prettier. Committing less files at the time is what finally "resolved" the issue.

blocks|key|651641|text|如果您正在使用替代命令行git客户端，例如hub，也会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|651642|几年来，我一直使用hub作为git的别名替代品，但最近我写了一个bash脚本，在其中做了大量的git工作，并开始遇到这个索引锁定问题。|651643|我无法找到修复，直到我记起我运行的是hub而不是git。我删除了它，问题就消失了！|651644|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/github/hub^0|L|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

This can also happen if you're using an alternate command line git client, like <a href="https://github.com/github/hub" rel="nofollow noreferrer">hub</a>.

I've been using hub as an aliased replacement for git for a couple of years, but recently wrote a bash script that does a bunch of git work in it, and started to get this index lock issue.

I couldn't find the fix until I remembered I was running hub instead of git. I removed that and the problem went away!

blocks|key|437357|text|你的代码是否在Dropbox正在同步的目录中？尝试暂停Dropbox。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|437358|我一直得到相同的情况，但一旦我暂停Dropbox+(界面提供了暂停30分钟，1小时，...)，它就再也没有发生过。|437359|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Is your code in a directory that Dropbox is syncing? Try pausing Dropbox.
I kept getting the same condition, but once I paused Dropbox (the interface gives you the option to pause for 30 minutes, 1 hour, ...), it never happened again.

blocks|key|437430|text|在我的例子中，只需转到project_path/.git并删除index.lock文件。试着推送你的代码，它会工作的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|437431|entityMap^0|B|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In My Case Simply go to <code>project_path/.git</code> and delete the index.lock file. try to push your code it will work.

When I do 'git commit', I'm getting the following:

<code>fatal: Unable to create 'project_path/.git/index.lock': File exists.</code>

However, when I do <code>ls project_path/.git/index.lock</code> it's saying the file doesn't exist. Any thoughts on what I should do? I've also noticed that project_path/.git is owned by root, not sure if that has anything to do with the problem I'm encountering.

git version is 1.7.5.4

edit: It seems that the problem most likely was another process I had running, that was writing (unbeknownst to me) to the project directory. I restarted my machine and then I had no problem committing.

git index.lock File exists when I try to commit, but cannot delete the file

Visual Studio

Windows

当我执行'git commit‘时，我得到了以下内容：fatal: Unable to create 'project_path/.git/index.lock': File exists.然而，当我执行ls project_path/.git/index.lock时，它会说该文件不存在。我该怎么做有什么想法吗？我还注...

问尝试提交但无法删除文件时，git index.lock文件存在
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试提交但无法删除文件时，git index.lock文件存在EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试提交但无法删除文件时，git index.lock文件存在
EN