From: Konstantin Khomoutov <kostix@bswap.ru>
To: Krishna Vivek Vitta <kvitta@microsoft.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git clone failure
Date: Tue, 24 Sep 2024 17:20:46 +0300 [thread overview]
Message-ID: <20240924142046.6wkhwnfd5vp5wh3y@carbon> (raw)
In-Reply-To: <SI2P153MB071833367C62DD94C96CF1F7D46F2@SI2P153MB0718.APCP153.PROD.OUTLOOK.COM>
On Mon, Sep 23, 2024 at 10:47:08AM +0000, Krishna Vivek Vitta wrote:
> We've seen multiple reports of git repositories failing to clone / getting
> corrupted in p9 file system. The mount points under this file system are
> marked for FANOTIFY to intercept file system events
>
> When we remove the marking on these mount points, git clone succeeds.
>
> Following is the error message:
[...]
> fatal: unknown error occurred while reading the configuration files
>
> Any reason why it is failing?
[...]
Are you able to build Git from the source?
As you can see in config.c, the error is reported in repo_read_config in the
case the function config_with_options, it calls, fails. Since it's not
expected to fail - except for some weird reasons, - you're probably dealing
with such a reason, and so you'd probably need to debug it yourself because I
hardly beleive it's easily possible for someone else to recreate your specific
setup. The debugging might be a simple "printf-style" one - that is, navigate
the call chain of these configuration-reading functions, stick calls to
printf() in places where some nested function returns a value indicating an
error exit, build, run, and see which of these printf() calls pinpoints the
failure. You will probably trace this to call to some C-library I/O function.
next prev parent reply other threads:[~2024-09-24 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 10:47 Git clone failure Krishna Vivek Vitta
2024-09-24 14:20 ` Konstantin Khomoutov [this message]
2024-09-24 21:45 ` brian m. carlson
2024-09-25 8:49 ` [EXTERNAL] " Krishna Vivek Vitta
2024-09-25 21:00 ` brian m. carlson
2024-09-26 7:11 ` Krishna Vivek Vitta
2024-09-26 11:54 ` brian m. carlson
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=20240924142046.6wkhwnfd5vp5wh3y@carbon \
--to=kostix@bswap.ru \
--cc=git@vger.kernel.org \
--cc=kvitta@microsoft.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox