Re: [msysGit] Running into issue: fatal: unable to write new index file

[Ciaran]

On Tue, Jul 17, 2012 at 8:40 PM, <matt....@gmail.com> wrote:

We're running into an issue with one of our large projects (17k files) where we hit the error:  fatal: unable to write new index file, git did not exit cleanly (exit code 128).  This seems to happen semi-randomly - sometimes switching branches and sometimes on pulls.  While this is random, I've seen it occur on every developer's machine at one point or another.  

At this point, I don't know what's left to try.  Has anyone run into this issue and solved it?  Any suggestions otherwise?

I've seen this behaviour when developers are using Git Extensions inside of visual studio, it appears to lock files within .git :(    

Have you used a tool like 'unlocker', or sysinternal's process explorer to see what locks are open in the folder when the problem happens ? 

- CJ.

[Matthew Mondok]

I actually used Unlocker to wipe out all the locks but that still didn't help.  I've also uninstalled Git Extensions, too.  The command line usually works, but after I get the failure message, even at the command line it tells me, "Rename from '.git/index.lock' to '.git/index' failed."  While I'd like to say we're only going to use the command line, that's going to be a problem for the full team at this point.  

Any other ideas?

[Matthew Mondok]

I'm also seeing this update using TortoiseGit outside of Visual Studio as well.