error: unable to create directory

1,494 views
Skip to first unread message

Michael Hipp

unread,
Mar 5, 2010, 10:31:20 PM3/5/10
to msy...@googlegroups.com
Anyone have any idea why I'm getting this?

git clone -q http://github.com/montylounge/django-sugar.git
C:\dev\virtenvs\redmule\src\django-sugar
error: unable to create directory for
C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD

The path exists up to c:\dev\virtenvs\redmule\src but it needs to create
the rest.

Any help appreciated.

Thanks,
Michael Hipp

Michael Hipp

unread,
Mar 6, 2010, 8:21:10 PM3/6/10
to msy...@googlegroups.com
Can anyone suggest a remedy for this? Git seems to be doing this on
every URL I've tried. So I'm kinda stuck.

Here's what I'm using:
>git --version
git version 1.6.5.1.1367.gcd48

Thanks,
Michael

Pat Thoyts

unread,
Mar 8, 2010, 5:37:42 AM3/8/10
to Michael Hipp, msy...@googlegroups.com
On 7 March 2010 01:21, Michael Hipp <Mic...@hipp.com> wrote:
>> git clone -q http://github.com/montylounge/django-sugar.git
>> C:\dev\virtenvs\redmule\src\django-sugar
>> error: unable to create directory for
>> C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD
>>
>> The path exists up to c:\dev\virtenvs\redmule\src but it needs to create
>> the rest.

Have you tried:

cd c:\dev\virtenvs\redmule\src
git clone http://github.com/montylounge/django-sugar.git django-sugar

Michael Hipp

unread,
Mar 8, 2010, 9:03:25 AM3/8/10
to msy...@googlegroups.com
On 3/8/2010 4:37 AM, Pat Thoyts wrote:
> On 7 March 2010 01:21, Michael Hipp<Mic...@hipp.com> wrote:
>>> error: unable to create directory for
>>> C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD
>>>
> Have you tried:
>
> cd c:\dev\virtenvs\redmule\src
> git clone http://github.com/montylounge/django-sugar.git django-sugar

Thanks. Same result:

--------------
C:\dev> cd c:\dev\virtenvs\redmule\src


c:\dev\virtenvs\redmule\src> git clone
http://github.com/montylounge/django-sugar.git django-sugar

error: unable to create directory for

c:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD
--------------

But I can do this, so it doesn't appear to be a permissions problem:
c:\dev\virtenvs\redmule\src> mkdir django-sugar\.git\HEAD

Any help?

Thanks,
Michael

Michael Hipp

unread,
Mar 9, 2010, 10:43:22 AM3/9/10
to msy...@googlegroups.com
On 3/5/2010 9:31 PM, Michael Hipp wrote:
> Anyone have any idea why I'm getting this?
>
> git clone -q http://github.com/montylounge/django-sugar.git
> C:\dev\virtenvs\redmule\src\django-sugar
> error: unable to create directory for
> C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD

Found why this is happening - Git evidently doesn't like NTFS symlinks.

c:\dev is a symlink
> dir c:\
02/25/2010 10:26 AM <SYMLINKD> dev [c:\dropbox\dev]
03/06/2010 05:58 PM <DIR> dropbox

When I change the above command to target
C:\dropbox\dev\virtenvs\redmule\src\django-sugar

instead of c:\dev\... it works fine.

Should I file a bug report on this? Is there a workaround that doesn't involve
messing up all my paths?

Thanks,
Michael

Erik Faye-Lund

unread,
Mar 9, 2010, 11:06:54 AM3/9/10
to Michael Hipp, msy...@googlegroups.com
On Tue, Mar 9, 2010 at 4:43 PM, Michael Hipp <Mic...@hipp.com> wrote:
> On 3/5/2010 9:31 PM, Michael Hipp wrote:
>>
>> Anyone have any idea why I'm getting this?
>>
>> git clone -q http://github.com/montylounge/django-sugar.git
>> C:\dev\virtenvs\redmule\src\django-sugar
>> error: unable to create directory for
>> C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD
>
> Found why this is happening - Git evidently doesn't like NTFS symlinks.
>
> c:\dev is a symlink
>> dir c:\
> 02/25/2010  10:26 AM    <SYMLINKD>     dev [c:\dropbox\dev]
> 03/06/2010  05:58 PM    <DIR>          dropbox
>
> When I change the above command to target
> C:\dropbox\dev\virtenvs\redmule\src\django-sugar
>
> instead of c:\dev\... it works fine.

I can't reproduce this. Cloning to a folder that is symlinked works
just fine for me. Even if I clone a subdir in my dropbox.

I had to switch away from that HTTP-link that you pointed to, because
it doesn't seem to work for me at all. I doubt that this should affect
the ability to create directories, though.

One thing, though. Do you have UAC enabled?

>
> Should I file a bug report on this? Is there a workaround that doesn't
> involve messing up all my paths?
>

I don't think there's any point in reporting it until we are sure that
cloning to NTFS symlinked dirs is an issue.

--
Erik "kusma" Faye-Lund

Michael Hipp

unread,
Mar 9, 2010, 12:11:01 PM3/9/10
to msy...@googlegroups.com
On 3/9/2010 10:06 AM, Erik Faye-Lund wrote:
> On Tue, Mar 9, 2010 at 4:43 PM, Michael Hipp<Mic...@hipp.com> wrote:
>> On 3/5/2010 9:31 PM, Michael Hipp wrote:
>>>
>>> Anyone have any idea why I'm getting this?
>>>
>>> git clone -q http://github.com/montylounge/django-sugar.git
>>> C:\dev\virtenvs\redmule\src\django-sugar
>>> error: unable to create directory for
>>> C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD
>>
>> Found why this is happening - Git evidently doesn't like NTFS symlinks.
>>
>> c:\dev is a symlink
>>> dir c:\
>> 02/25/2010 10:26 AM<SYMLINKD> dev [c:\dropbox\dev]
>> 03/06/2010 05:58 PM<DIR> dropbox
>>
>> When I change the above command to target
>> C:\dropbox\dev\virtenvs\redmule\src\django-sugar
>>
>> instead of c:\dev\... it works fine.
>
> I can't reproduce this. Cloning to a folder that is symlinked works
> just fine for me. Even if I clone a subdir in my dropbox.
>
> I had to switch away from that HTTP-link that you pointed to, because
> it doesn't seem to work for me at all. I doubt that this should affect
> the ability to create directories, though.
>
> One thing, though. Do you have UAC enabled?

Both my systems that are seeing this issue are on Windows 7, UAC isn't exactly
on/off anymore. Mine is set at the default of "notify me only when programs try
to change windows".

Anyway, I set the slider to its lowest level ("never notify me"), rebooted, and
tried again. The error still persists.

Xavier Vergés

unread,
Mar 12, 2010, 6:31:24 AM3/12/10
to msysGit
Hello

I'm getting the same error, about the HEAD dir creation

I'm on Windows Vista
$ git --version
git version 1.7.0.2.msysgit.0

new to git, doing
$ git clone git://github.com/schacon/simplegit-progit.git

My symlink was not created using any cygwin feature. This was also in
a dir originally inside dropbox (that turned off during the test just
in case)

Thanks in advance for any hint.

-Xavier

On Mar 9, 6:11 pm, Michael Hipp <Mich...@Hipp.com> wrote:
> On 3/9/2010 10:06 AM, Erik Faye-Lund wrote:
>
>
>
>
>
> > On Tue, Mar 9, 2010 at 4:43 PM, Michael Hipp<Mich...@hipp.com>  wrote:
> >> On 3/5/2010 9:31 PM, Michael Hipp wrote:
>
> >>> Anyone have any idea why I'm getting this?
>

> >>> git clone -qhttp://github.com/montylounge/django-sugar.git


> >>> C:\dev\virtenvs\redmule\src\django-sugar

> >>> error: unable tocreatedirectory for


> >>> C:/dev/virtenvs/redmule/src/django-sugar/.git/HEAD
>
> >> Found why this is happening - Git evidently doesn't like NTFS symlinks.
>
> >> c:\dev is a symlink
> >>>dirc:\
> >> 02/25/2010  10:26 AM<SYMLINKD>       dev [c:\dropbox\dev]
> >> 03/06/2010  05:58 PM<DIR>            dropbox
>
> >> When I change the above command to target
> >> C:\dropbox\dev\virtenvs\redmule\src\django-sugar
>
> >> instead of c:\dev\... it works fine.
>
> > I can't reproduce this. Cloning to a folder that is symlinked works
> > just fine for me. Even if I clone a subdir in my dropbox.
>
> > I had to switch away from that HTTP-link that you pointed to, because
> > it doesn't seem to work for me at all. I doubt that this should affect

> > the ability tocreatedirectories, though.

Michael Hipp

unread,
Mar 14, 2010, 2:05:14 PM3/14/10
to msy...@googlegroups.com
On 3/9/2010 10:06 AM, Erik Faye-Lund wrote:
> On Tue, Mar 9, 2010 at 4:43 PM, Michael Hipp<Mic...@hipp.com> wrote:
>> Found why this is happening - Git evidently doesn't like NTFS symlinks.
>
> I can't reproduce this. Cloning to a folder that is symlinked works
> just fine for me. Even if I clone a subdir in my dropbox.

This sequence of commands seems to reproduce the problem faithfully on
my 2 systems (you have to run this in an "administrator" shell for
mklink to work):

This fails:
-----------
> cd \
> mkdir c:\foo\bar\src
> mklink /d bar c:\foo\bar
symbolic link created for bar <<===>> c:\foo\bar
> git clone -q http://github.com/montylounge/django-sugar.git C:\bar\src
error: unable to create directory for C:/bar/src/.git/HEAD

This works:
-----------
> cd \
> mkdir c:\foo\bar\src
> mklink /d bar c:\foo\bar
symbolic link created for bar <<===>> c:\foo\bar

C:\foo\bar\src

Note that DropBox isn't involved in this example.

These systems are both Win 7 Ultimate; one is x32, one is x64.

Thanks,
Michael

Erik Faye-Lund

unread,
Mar 14, 2010, 3:00:11 PM3/14/10
to Michael Hipp, msy...@googlegroups.com
On Sun, Mar 14, 2010 at 7:05 PM, Michael Hipp <Mic...@hipp.com> wrote:
> On 3/9/2010 10:06 AM, Erik Faye-Lund wrote:
>>
>> On Tue, Mar 9, 2010 at 4:43 PM, Michael Hipp<Mic...@hipp.com>  wrote:
>>>
>>> Found why this is happening - Git evidently doesn't like NTFS symlinks.
>>
>> I can't reproduce this. Cloning to a folder that is symlinked works
>> just fine for me. Even if I clone a subdir in my dropbox.
>
> This sequence of commands seems to reproduce the  problem faithfully on my 2
> systems (you have to run this in an "administrator" shell for mklink to
> work):
>
> This fails:
> -----------
>> cd \
>> mkdir c:\foo\bar\src
>> mklink /d bar c:\foo\bar
> symbolic link created for bar <<===>> c:\foo\bar
>> git clone -q http://github.com/montylounge/django-sugar.git C:\bar\src
> error: unable to create directory for C:/bar/src/.git/HEAD
>

This works just fine for me:

---8<---
C:\Users\kusma>cd \

C:\>mkdir c:\foo\bar\src

C:\>mklink /d bar c:\foo\bar


symbolic link created for bar <<===>> c:\foo\bar

C:\>git clone -q http://github.com/montylounge/django-sugar.git C:\foo\bar\src

C:\>
---8<---

--
Erik "kusma" Faye-Lund

Erik Faye-Lund

unread,
Mar 14, 2010, 3:02:39 PM3/14/10
to Michael Hipp, msy...@googlegroups.com

Stupid me, I copied the wrong command-line. However, cloning to
C:\bar\src works just fine for me as well.


--
Erik "kusma" Faye-Lund

Michael Hipp

unread,
Mar 15, 2010, 7:58:36 PM3/15/10
to msy...@googlegroups.com

What version of Windows are you using?

Can we post this as a bug? It is utterly repeatable on my systems. Is
there some way to debug it?

Thanks,
Michael

Erik Faye-Lund

unread,
Mar 15, 2010, 8:42:27 PM3/15/10
to Michael Hipp, msy...@googlegroups.com
On Tue, Mar 16, 2010 at 12:58 AM, Michael Hipp <Mic...@hipp.com> wrote:
> What version of Windows are you using?
>

Vista 64.

> Can we post this as a bug?

I think that would make sense.

> It is utterly repeatable on my systems. Is there
> some way to debug it?
>

The first step would be to install the full msysGit development
environment (if you haven't already), i.e. the "netinstall".

Second you should add a config.mak file that contains something like
"CFLAGS += -g", and run "make install"

Then you can start run git clone through GDB, and set a break-point in
the die-function. There you should be able to see what line of code
the error occurred on. Having that, it should be possible to analyze
the code by stepping through it.

--
Erik "kusma" Faye-Lund

Johannes Schindelin

unread,
Mar 15, 2010, 8:48:50 PM3/15/10
to Michael Hipp, Erik Faye-Lund, msy...@googlegroups.com
Hi,

Michael, culling the Cc: list only shows that you did not do your
homework. If you want to be taken seriously, stop it.

On Mon, 15 Mar 2010, Michael Hipp wrote:

> On 3/14/2010 2:02 PM, Erik Faye-Lund wrote:
>

> > [...] cloning to C:\bar\src works just fine for me as well.


>
> What version of Windows are you using?

Erik is known, really known, to be an active msysGit contributor, so I
would be amazed to learn that he failed to update to the current 'devel'
in both msysgit.git and 4msysgit.git.

So you can be pretty sure that Erik's analysis stems from a _bleeding
edge_ system.

Ciao,
Dscho

Erik Faye-Lund

unread,
Mar 15, 2010, 9:06:55 PM3/15/10
to Michael Hipp, msy...@googlegroups.com
On Tue, Mar 16, 2010 at 1:42 AM, Erik Faye-Lund
<kusm...@googlemail.com> wrote:
> On Tue, Mar 16, 2010 at 12:58 AM, Michael Hipp <Mic...@hipp.com> wrote:
>> What version of Windows are you using?
>>
>
> Vista 64.
>

...aaaand, after installing msysGit on my Win7-machine, I can now
reproduce this issue. So this seems to be yet another Git vs Win7
issue.

Now, I don't have time to look at this any time soon, too many other
things that are overdue, so the best would be if you're able to poke
around a bit yourself. Just post here if you find out or wonder about
something, and I'm sure we'll figure it out.

--
Erik "kusma" Faye-Lund

Johannes Schindelin

unread,
Mar 16, 2010, 3:12:14 AM3/16/10
to Michael Hipp, Erik Faye-Lund, msy...@googlegroups.com
Hi,

On Mon, 15 Mar 2010, Michael Hipp wrote:

> On 3/15/2010 7:48 PM, Johannes Schindelin wrote:
>
> > Michael, culling the Cc: list only shows that you did not do your
> > homework. If you want to be taken seriously, stop it.
>

> Homework?
>
> I'm not sure what sort of "homework" I was supposed to do here, or
> perhaps I just don't understand what you're ripping into me about.

It's related to the saying "when in Rome, do as the Romans".

> > On Mon, 15 Mar 2010, Michael Hipp wrote:
> > > What version of Windows are you using?
> >
> > Erik is known, really known, to be an active msysGit contributor, so I
> > would be amazed to learn that he failed to update to the current
> > 'devel' in both msysgit.git and 4msysgit.git.
>

> I said or asked nothing about his version of msysgit.

I am terribly sorry. Somehow my eyes read "Git for Windows" when there is
only "Windows".

My apologies,
Dscho

Michael Hipp

unread,
Mar 15, 2010, 10:14:10 PM3/15/10
to Johannes Schindelin, Erik Faye-Lund, msy...@googlegroups.com
On 3/15/2010 7:48 PM, Johannes Schindelin wrote:
> Hi,
>
> Michael, culling the Cc: list only shows that you did not do your
> homework. If you want to be taken seriously, stop it.

Homework?

I'm not sure what sort of "homework" I was supposed to do here, or
perhaps I just don't understand what you're ripping into me about.

I hit "Reply List" in Thunderbird and the message went to the list as
I've always been told was the proper etiquette rather than sending it
directly to everyone's inbox. That's been proper protocol on every list
I can remember, oh, these last 17 years or so.

But if you want me to always use the less accessible "Reply All"
function I shall try to remember to do so on /this/ list. Happy?
(Personally, I'd prefer not to get 2 copies of every message, but
evidently that's an individual thing.)

> On Mon, 15 Mar 2010, Michael Hipp wrote:
>> What version of Windows are you using?
>
> Erik is known, really known, to be an active msysGit contributor, so I
> would be amazed to learn that he failed to update to the current 'devel'
> in both msysgit.git and 4msysgit.git.

I said or asked nothing about his version of msysgit. Nor can I find
anything disrespectful in the question I asked Erik. Again, I don't know

what you're ripping into me about.

> So you can be pretty sure that Erik's analysis stems from a _bleeding
> edge_ system.

I was just curious as to whether or not he was on Windows 7. We now know
he is on Vista x64. And it appears, from his testing, that the problem
is indeed specific to Win7. Which, ahem, makes my question seem all the
more appropriate now doesn't it.

Good day,
Michael

Reply all
Reply to author
Forward
0 new messages