From: Jeff King <peff@peff.net>
To: Alex Nauda <alex@alexnauda.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>, git@vger.kernel.org
Subject: Re: on Amazon EFS (NFS): "Reference directory conflict: refs/heads/" with status code 128
Date: Wed, 24 Aug 2016 17:39:01 -0400 [thread overview]
Message-ID: <20160824213900.gcnwxu46zvgpjr5a@sigill.intra.peff.net> (raw)
In-Reply-To: <CAMQLHmAraXPL=8SmMG4X_424FAzx4q2Byk8pva5wEOg7vNSqLw@mail.gmail.com>
On Wed, Aug 24, 2016 at 04:52:33PM -0400, Alex Nauda wrote:
> Elastic File System (EFS) is Amazon's scalable filesystem product that
> is exposed to the OS as an NFS mount. We're using EFS to host the
> filesystem used by a Jenkins CI server. Sometimes when Jenkins tries
> to git fetch, we get this error:
> $ git -c core.askpass=true fetch --tags --progress
> git@github.com:mediasilo/dodo.git
> +refs/pull/*:refs/remotes/origin/pr/*
> fatal: Reference directory conflict: refs/heads/
> $ echo $? 128
>
> Has anyone seen anything like this before? Any tips on how to troubleshoot it?
No, I haven't seen it before. That's an internal assertion in the refs
code that shouldn't ever happen. It looks like it happens when the loose
refs end up with duplicate directory entries. While a bug in git is an
obvious culprit, I wonder if it's possible that your filesystem might
expose the same name twice in one set of readdir() results.
+cc Michael, who added this assertion long ago (and since this is the
first report in all these years, it does make me suspect that the
filesystem is a critical part of reproducing).
-Peff
next prev parent reply other threads:[~2016-08-24 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 20:52 on Amazon EFS (NFS): "Reference directory conflict: refs/heads/" with status code 128 Alex Nauda
2016-08-24 21:39 ` Jeff King [this message]
2016-08-25 6:28 ` Michael Haggerty
2016-08-25 16:01 ` Alex Nauda
2016-08-26 0:06 ` Michael Haggerty
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160824213900.gcnwxu46zvgpjr5a@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=alex@alexnauda.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).