Git: fatal: could not set 'core.filemode' to 'true'

Question

When trying to clone a repository with a command like:

git clone ssh://myuserid@myhost/mypath/myrepo.git

I'm getting the following errors:

Cloning into 'myrepo'...

error: failed to write new configuration file /path/myrepo/.git/config.lock

fatal: could not set 'core.filemode' to 'true'

Any ideas what the problem could be? A Google search yielded nothing.

Yes, I have write access to the destination folder. In fact, I can successfully execute the following commands:mkdir -p /path/myrepo/.git; touch /path/myrepo/.git/config.lock; — Josh Johnson, Sep 13 '18 at 13:58
Try cloning to a completely different place. One you _know_ you have access to. — evolutionxbox, Sep 13 '18 at 14:05
When I try cloning in my home directory, the clone seems to make more progress but fails because there is not enough disk space on the home directory's partition. So I think evolutionxbox is on to something. Maybe there's something fishy about the destination. — Josh Johnson, Sep 13 '18 at 14:29
https://stackoverflow.com/search?q=%5Bgit%5D+fatal%3A+could+not+set+%27core.filemode%27+to+%27true%27 — phd, Sep 13 '18 at 14:30

score 0 · Answer 1 · edited Sep 14 '18 at 05:17

0

It appears that the problem was that the original target partition had insufficient disk space. I don't understand why the error message did not indicate that, but once I mounted a device at /path that had plenty of space all was well.

edited Sep 14 '18 at 05:17

franiis

1,378
1
18
33

answered Sep 13 '18 at 16:27

Josh Johnson

11
1
3

Git: fatal: could not set 'core.filemode' to 'true'

1 Answers1