From: Zenobiusz Kunegunda <zenobiusz.kunegunda@interia.pl>
To: "René Scharfe" <l.s.r@web.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 |
Date: Tue, 14 Mar 2017 16:25:50 +0100 [thread overview]
Message-ID: <jwwousyentaeeuvbaznm@xjvs> (raw)
In-Reply-To: <b9dc5b05-46e6-a3d7-2fb0-638bff2da676@web.de>
Output of
truss git status 2>&1 >/dev/null |grep chdir
is empty when git status fails.
Also git status succeeded when run as root.Od: "René Scharfe" <l.s.r@web.de>
Do: "Zenobiusz Kunegunda" <zenobiusz.kunegunda@interia.pl>;
Wysłane: 18:32 Poniedziałek 2017-03-13
Temat: Re: fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 |
>
>> Am 13.03.2017 um 13:23 schrieb Zenobiusz Kunegunda:
>> Tested on ZFS filesystem
>>
>>
>>
>> [test0@s0]:<~>$ mkdir '232222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222'
>> [test0@s0]:<~>$ cd 232222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222/
>> [test0@s0]:<~/232222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222>$ git status
>> fatal: Unable to read current working directory: Permission denied
>>
>> [test0@s0]:<~/232222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222>$ git blahblahblah
>> fatal: Unable to read current working directory: Permission denied
>>
>>
>> But when I create directory with same name (232...) as it's subdirectory everything works as expected inside that subdirectory.
>
> Earlier I checked on UFS. Now I tried the above commands on ZFS,
> but they work as expected:
>
> $ git status
> fatal: Not a git repository (or any parent up to mount point /src)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
>
> Git checks out if it's in a git repository and if the current
> working directory isn't one then it goes to the parent directories
> recursively until it finds the root of a repo or a file system
> boundary or / (root).
>
> You can see where your invocation goes to with:
>
> $ strace git status 2>&1 >/dev/null | grep chdir
>
> René
>
>
next prev parent reply other threads:[~2017-03-14 15:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 16:10 fatal: Could not get current working directory: Permission denied | affected 2.10,2.11,2.12, but not 1.9.5 | Zenobiusz Kunegunda
2017-03-08 17:36 ` René Scharfe
2017-03-09 11:01 ` Zenobiusz Kunegunda
2017-03-11 21:17 ` René Scharfe
2017-03-13 12:23 ` Zenobiusz Kunegunda
2017-03-13 17:31 ` René Scharfe
2017-03-14 15:25 ` Zenobiusz Kunegunda [this message]
2017-03-13 13:23 ` Zenobiusz Kunegunda
2017-03-13 21:31 ` René Scharfe
2017-03-14 7:44 ` Zenobiusz Kunegunda
2017-03-14 17:59 ` René Scharfe
2017-03-15 9:44 ` Zenobiusz Kunegunda
2017-03-15 21:30 ` René Scharfe
2017-03-17 19:34 ` René Scharfe
2017-03-17 19:45 ` Stefan Beller
2017-03-17 21:07 ` René Scharfe
2017-03-17 22:29 ` Jeff King
2017-03-17 22:50 ` René Scharfe
2017-03-21 13:29 ` Zenobiusz Kunegunda
2017-03-21 19:04 ` René Scharfe
2017-03-22 8:30 ` Zenobiusz Kunegunda
2017-03-21 10:08 ` Zenobiusz Kunegunda
2017-03-09 11:11 ` Zenobiusz Kunegunda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwwousyentaeeuvbaznm@xjvs \
--to=zenobiusz.kunegunda@interia.pl \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.