blocks|key|582838|text|当进程没有释放这些文件的句柄时，我通常会看到这种类型的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|582839|请确保未运行任何内容，然后再次尝试结帐。|582840|注意:这也可能与Git的安装方式有关(在Windows上，如果msysgit安装在C:\Program或C:\Program+Files中，则UAC可能会产生问题，请参阅"msysgit+-+sh.exe+-+fork:+Permission+denied+-+Vista+64+bit“和comment+2+of+issue+437)|offset|length|style|CODE|582841|注意:与illustrated+below一样，问题的另一个常见原因是目录上的权限问题(错误的所有者)，而不一定是无法取消链接的文件上的权限问题。|582842|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2439336/msysgit-sh-exe-fork-permission-denied-vista-64-bit|1|http://code.google.com/p/msysgit/issues/detail?id=437#c2|2|https://stackoverflow.com/a/16105533/6309^0|0|0|15|A|1G|G|2E|1L|0|41|M|1|0|4|H|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@$F|10|G|11|H|I]|$F|12|G|13|H|I]]|9|@$F|14|G|15|1|16]|$F|17|G|18|1|19]]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|L|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]]]

I usually see that kind of error when there is a process not releasing the handle of those files.

Make sure nothing is running, and then try your checkout again.

Note: it can also be related with the way Git has been installed (on Windows, UAC can generate problem if msysgit is installed in <code>C:\Program</code> or <code>C:\Program Files</code>, see "<a href="https://stackoverflow.com/questions/2439336/msysgit-sh-exe-fork-permission-denied-vista-64-bit">msysgit - sh.exe - fork: Permission denied - Vista 64 bit</a>" and <a href="http://code.google.com/p/msysgit/issues/detail?id=437#c2" rel="noreferrer">comment 2 of issue 437</a>)

Note: as <a href="https://stackoverflow.com/a/16105533/6309">illustrated below</a>, a common other cause of the problem is rights issue on the directory (wrong owner), not necessarily on the file that can't be unlinked.

blocks|key|798967|text|在这种情况下，"Unlink“本质上是”删除文件“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|798968|这个错误不是由git本身引起的。在命令行或文件资源管理器中手动删除这些文件时，应该会出现类似的错误。|798969|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|$]]

"Unlink" essentially means "delete file" in this case. 

This error is not caused by git itself. You should have similar errors deleting those files manually, in a command line or file explorer.

blocks|key|582959|text|在Drupal7中，我遇到了一个default-settings.php文件的问题。在这种情况下，我无法像@rtconner所说的那样删除或恢复它。我没有使用这个文件的应用程序或任何东西，它最终是一个权限错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|582960|我将chmod+777+*添加到文件夹中，然后我可以恢复它，没有问题。|offset|length|style|CODE|582961|entityMap^0|0|2|B|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]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I was having the issue with a default-settings.php file in drupal 7. In this case I wasn't able to delete it or revert it just like @rtconner said. I didn't have an application or anything using this file, and it ended up being a permissions error.

I added <code>chmod 777 *</code> to the folder and then I was able to revert it no problem.

blocks|key|799063|text|在我第一次遇到这个错误时，我的用户有权“写”到文件，但没有“写”到包含的目录。检查文件所在目录的权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799064|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 first encounter with this error my user had rights to "write" to the file but not the containing directory. Check the permissions of the directory containing the file.

blocks|key|583031|text|在我的例子中，它是文件夹名称中的":“字符，防止了git存储库在windows上结帐。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|583032|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 it was a ":" character in a folder name prevenitng the git repo to checkout on windows.

blocks|key|583049|text|您没有访问权限，可能是因为您不是所有者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|583050|通过将所有者更改为您自己来修复：|583051|sudo+chown+-R+your_login_name+/path/to/folder|code-block|syntax|javascript|583052|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You don't have the access permission, maybe because you are not the owner.

Fix by changing the owner to yourself:

<pre><code>sudo chown -R your_login_name /path/to/folder
</code></pre>

blocks|key|583088|text|确保所有关联的进程或线程都未运行，并根据需要执行结束任务或强制退出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|583089|确保您更改了所有权权限。|583090|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|$]]

Make sure that any associated processes or threads are not running and perform end task or force quit as necessary.

Make sure you change the ownership permission.

blocks|key|799218|text|每当在我的OS机器上运行"git+repack“或"git”时，我都会遇到这个问题，即使是在以管理员权限运行git时也是如此，在遇到这个页面后，我终于解决了这个问题：http://hints.macworld.com/comment.php?mode=view&cid=1734|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|799219|修复方法是打开一个终端，转到您的git存储库，cd进入.git文件夹，然后执行以下操作：|799220|chflags+-R+nouchg+*|code-block|syntax|javascript|799221|如果这就是问题所在，那么在那之后，您的git命令将正常工作。|799222|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20141112125619/http://hints.macworld.com/comment.php?mode=view&cid=1734^0|2B|1K|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

I ran into this problem whenever running "git repack" or "git gc" on my OS X machines, even when running git with admin privileges, and I finally solved it after coming across this page: <a href="https://web.archive.org/web/20141112125619/http://hints.macworld.com/comment.php?mode=view&amp;cid=1734" rel="nofollow noreferrer">http://hints.macworld.com/comment.php?mode=view&amp;cid=1734</a>

The fix is to open a terminal, go to your git repo, cd into the .git folder, and then do:

<pre><code>chflags -R nouchg *
</code></pre>

If that was the issue, then after that, your git commands will work as normal.

blocks|key|583196|text|我只需将用户从ubuntu切换到我最初使用的实际用户名。这解决了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|583197|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 just had to switch user from ubuntu to my actual user name that I'd first done stuff under. That fixed it.

blocks|key|799333|text|通过将我的git客户端(GitExtensions)设置为始终在管理模式下运行，为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799334|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|$]]

Solved for me by setting my git client (GitExtensions) to always run in admin mode.

blocks|key|583268|text|我在使用IntelliJ+(14.1.3旗舰版)时遇到了这个问题，我想还原一些文件中的更改。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|583269|通过关闭在另一个窗口中打开的Git+Bash解决了问题-+IntelliJ中的另一个恢复试验起作用了。|583270|entityMap^0|4|8|0|E|8|T|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

I had that problem while using <code>IntelliJ</code> (14.1.3 Ultimate), I wanted to revert changes in some file. 

Solved by closing <code>Git Bash</code> opened in another window - another revert trial in <code>IntelliJ</code> worked.

blocks|key|799436|text|您可以更改写权限以完成此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799437|sudo+chmod+-R+ug%2Bw+.+|code-block|syntax|javascript|799438|此命令将授予'w'对当前目录中所有文件夹的权限。|offset|length|style|CODE|799439|entityMap^0|0|0|6|3|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You can change the write permissions to get it done.

<pre><code>sudo chmod -R ug+w . 
</code></pre>

This command will give <code>'w'</code> permissions to all the folders in the current directory.

blocks|key|583378|text|当我尝试执行git+reset+--hard时，我在虚拟机(运行Ubuntu)中遇到了这个错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|583379|修复方法很简单，就是从OS+X主机运行git+reset+--hard。|583380|entityMap^0|6|G|0|J|G|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I had this error inside a virtual machine (running Ubuntu), when I tried to do <code>git reset --hard</code>.

The fix was simply to run <code>git reset --hard</code> from the OS X host machine instead.

blocks|key|799506|text|其他建议都没有对我起作用，但这一点起到了作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799507|sudo+git+reflog+expire+--expire=now+--all+&&+sudo+git+gc+--prune=now+--aggressive|offset|length|style|CODE|799508|entityMap^0|0|0|29|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]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

None of the other suggestions worked for me, but this did:

<code>sudo git reflog expire --expire=now --all &amp;&amp; sudo git gc --prune=now --aggressive</code>

blocks|key|583475|text|我遇到了这个错误，我认为问题是当我启动Eclipse并创建文件时，我必须‘以管理员身份运行’，因此它们归管理员所有(注意，在文件夹上运行'ls+-la‘)。当我后来试图隐藏这些文件时，它不让我这么做(‘无法取消文件链接’之类的)。对文件执行chmod是我的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|583476|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 encountered this error and I think the issue was that I had 'run as admin' when I started Eclipse and created the files, therefore they were owned by Admin (noticed by running 'ls -la' on the folder). When I later tried to stash the files, it didn't let me ('unable to unlink files' and all that). Doing a chmod on the files was the fix for me.

blocks|key|799673|text|git+gc为我工作(在一个新的选项卡中)。每次改垒都会得到这样的结果。谢谢http://www.saintsatplay.com/blog/2016/02/dealing-with-git-unlink-file-errors#.W4WWNZMzZZJ|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|799674|entityMap|0|LINK|mutability|MUTABLE|url|http://www.saintsatplay.com/blog/2016/02/dealing-with-git-unlink-file-errors#.W4WWNZMzZZJ^0|12|2H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

git gc worked for me (in a new tab). Was getting this with every rebase. Thanks <a href="http://www.saintsatplay.com/blog/2016/02/dealing-with-git-unlink-file-errors#.W4WWNZMzZZJ" rel="nofollow noreferrer">http://www.saintsatplay.com/blog/2016/02/dealing-with-git-unlink-file-errors#.W4WWNZMzZZJ</a>

blocks|key|799757|text|你需要做的就是提供权限，从你的项目根目录运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799758|++++chmod+ug%2Bw+<directory+path>|code-block|syntax|javascript|799759|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

All you need to do is provide permissions, run the command below from the root of your project:

<pre><code> chmod ug+w &lt;directory path&gt;
</code></pre>

blocks|key|799818|text|我也有同样的问题，我尝试了其他人建议的一些替代方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799819|但最终给.git文件夹正确的权限就解决了问题。|799820|sudo+chown+-R+"${USER:-$(id+-un)}"+.git|code-block|syntax|javascript|799821|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had the same issue , I tried few alternatives as others suggested.

But finally giving correct permission to .git folder solve the issues.

<pre><code>sudo chown -R "${USER:-$(id -un)}" .git
</code></pre>

blocks|key|583832|text|在我的例子中，通过将www-data设置为所有者解决了权限问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|583833|chown+-R+www-data+project_folder_name|code-block|syntax|javascript|583834|entityMap^0|A|8|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

In my case the permission problem solved by setting <code>www-data</code> as an owner:

<pre><code>chown -R www-data project_folder_name
</code></pre>

blocks|key|799965|text|在我的例子中，我的Windows目录在Dropbox文件夹下。这不是Git特有的问题。当一个文件(在本例中是锁文件)刚刚创建完成时，Dropbox会再花一秒钟时间进行同步。在此期间，Dropbox正在使用该文件，任何第三方程序(在本例中为Git)都无法删除该文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|799966|我的解决方案是退出Dropbox，从而避免Dropbox文件同步的幕后魔术。|799967|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|$]]

In my case, my Windows directory is under the Dropbox folder. It is not a Git-specific issue. When a file (in this case, the lock file) has just been created, it takes Dropbox another second to do the synchronization. During that time, the file is in use by Dropbox, and any 3rd party program (in this case, Git) cannot delete the file.

My solution is to quit Dropbox and therefore avoiding the behind-the-scenes magic of Dropbox's file synch.

blocks|key|800012|text|我在windows机器上运行Git+Bash时遇到了这个错误。在我的特殊情况下，我只需要以管理员身份打开Git+Bash。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|800013|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've encountered this error while running Git Bash on a windows box. In my particular case I just needed to open Git Bash as administrator.

blocks|key|800065|text|对我来说，在消息的顶部是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|800066|Auto+packing+the+repository+in+background+for+optimum+performance.
See+"git+help+gc"+for+manual+housekeeping.
error:+The+last+gc+run+reported+the+following.+Please+correct+the+root+cause
and+remove+.git/gc.log.
Automatic+cleanup+will+not+be+performed+until+the+file+is+removed.|code-block|syntax|javascript|800067|所以我用rm+.git/gc.log删除了这个文件，然后我得到了：|offset|length|style|CODE|800068|Auto+packing+the+repository+in+background+for+optimum+performance.
See+"git+help+gc"+for+manual+housekeeping.
error:+The+last+gc+run+reported+the+following.+Please+correct+the+root+cause
and+remove+.git/gc.log.
Automatic+cleanup+will+not+be+performed+until+the+file+is+removed.

warning:+There+are+too+many+unreachable+loose+objects;+run+'git+prune'+to+remove+them.|800069|运行git+prune后，一切都恢复正常。|800070|entityMap^0|0|0|4|E|0|0|2|9|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

For me, at the top of the message there was:
<pre><code>Auto packing the repository in background for optimum performance.
See &quot;git help gc&quot; for manual housekeeping.
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.
</code></pre>
So I removed the file with <code>rm .git/gc.log</code>, and then I got:
<pre><code>Auto packing the repository in background for optimum performance.
See &quot;git help gc&quot; for manual housekeeping.
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.
</code></pre>
After running <code>git prune</code>, everything was back to normal.

blocks|key|584101|text|我解决了这个问题，只需删除所有临时数据>+Run>%25temp%25+>按enter并删除所有临时文件，然后重新启动计算机。对我来说，它现在起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|584102|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 solved this problem, just by delete all temp data &gt; Run&gt;%temp% &gt;Hit enter and delete all temp files and restarting the computer. For me it is working now.

I am aware that there are similar issues about git relating to the 'unable to unlink' warning, but I have not been able to use them.

The main difference is that this happened when I have not been dealing with submodules in any way (I have never dealt with them before). I created a branch called 'upgrade', deleted my old framework files, and copied in the new ones. I used git add -A, then committed everything. When I tried to checkout the trunk branch, it responded with the following errors:

<pre><code>warning: unable to unlink requirements/views/sk/index.php: Permission denied
warning: unable to unlink requirements/views/sv/index.php: Permission denied
warning: unable to unlink requirements/views/zh/index.php: Permission denied
warning: unable to unlink requirements/views/zh_cn/index.php: Permission denied
warning: unable to unlink requirements/views/zh_tw/index.php: Permission denied
</code></pre>

...etc. There are hundreds of them.

At first I thought this was simply a permissions problem, and so I added group write permissions to the entire requirements directory recursively, but there was no change.

Edit: As suggested in an answer below, I attempted to do the same thing but with everything else closed. I had no more luck than before.

This issue is particularly debilitating as I cannot move to trunk to get back to normal development.

Git Checkout warning: unable to unlink files, permission denied

虚拟机

Windows

Eclipse

Ubuntu

我知道git上也有类似的问题，与“无法解除链接”的警告有关，但我一直无法使用它们。主要的区别是，当我没有以任何方式处理子模块(我以前从未处理过它们)时，会发生这种情况。我创建了一个名为“upgrade”的分支，删除了旧的框架文件，并复制了新的文件。我使用git添加-A，然后提交所有内容。当我尝试签出中继分支时，它响应了...

问Git签出警告:无法取消文件链接，权限被拒绝
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Git签出警告:无法取消文件链接，权限被拒绝EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Git签出警告:无法取消文件链接，权限被拒绝
EN