GIT: “fatal: unable to write new_index file” while commit?

As this thread illustrates this is usually a disk space issue.

As this thread illustrates, this is usually a disk space issue: $ git status fatal: unable to write new_index file One cause of this that I found was that my file system had run out of space. Finding large directories with something like the following helped clean up some log files that had run wild : $ du -h / | grep ^0-9. *G Note: you can also see it for a resource issue with msysgit and Egit (Git for Eclipse): Problem still remained so I ran File Monitor from Sysinternals Suite.It seems that Eclipse is accessing index file constantly and blocks command line git for a classic anti-virus issue: Yeah, looks like Windows Defender strikes again.

I always forget to disable that damn thing. I can't believe how broken it is. Destroys Blu-ray playback at home, breaks Git at work...

I have found solution. Just need to free some disk space.

I was writing the same thing;) – VonC Sep 15 '10 at 6:03.

I was getting the same error while I was merging a git repo that was sshfs mounted. There was no shortage of space anywhere. In my case the solution was to add an -o workaround=rename option to the sshfs mount command.

Like so: sshfs -o idmap=user -o uid=lokal uid -o gid=lokal gid -o workaround=rename host: mountpoint.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.