All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Hodique <yann.hodique@gmail.com>
To: git@vger.kernel.org
Subject: consistency problem on ZFS
Date: Sun, 28 Apr 2013 20:11:25 +0100	[thread overview]
Message-ID: <m2bo8yxyg2.fsf@jarvis.hodique.info> (raw)

Hi,

I have a weird problem that seems to manifest itself only on ZFS
(actually the Zevo distribution, on OSX). With git 1.8.2.1 by the way.
I just switched to ZFS, so I can't blame that particular version of git.

"Sometimes" (I'd say something like 10-15% of the time, fairly
reproducible anyway), "git diff-files" will see changes that don't exist
for some time, then will catch up with the actual state of the file:

$ git checkout next; git diff-files; git checkout next; git diff-files
Already on 'next'
:100644 100644 bd774cccaa14e061c3c26996567ee28f4f77ec80 0000000000000000000000000000000000000000 M	magit.el
Already on 'next'
$

Here it was pretty quick, but sometimes I would see those phantom
diffs for more than 5 seconds.

Interestingly, if I manage to run "git diff" during that time, this one
reports no changes. See https://gist.github.com/sigma/5477827 for a more
complex trace: "git merge" was complaining about changes, yet neither "git
diff" nor "git status" did show any. That's the scenario I tried to
minimize to the invocation above.

I'm willing to accept that the filesystem has some responsibility there,
but the inconsistency bothers me. Anything I can provide to help finding
the root cause of the issue ?

Thanks for any hint (and workarounds are highly welcome, as it breaks
many of my scripts, and magit too :))

Yann.

-- 
A Duke must always take control of his household, for if he does not
rule those closest to him, he cannot hope to govern a planet.

  -- DUKE PAULUS ATREIDES

             reply	other threads:[~2013-04-28 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 19:11 Yann Hodique [this message]
2013-04-28 19:33 ` consistency problem on ZFS Thomas Rast
2013-04-28 19:44   ` Yann Hodique
2013-04-28 20:12 ` John Szakmeister
2013-04-28 20:21   ` Yann Hodique
2013-04-28 21:33 ` Junio C Hamano
2013-04-29 17:55   ` Yann Hodique
2013-04-29 18:01     ` Junio C Hamano
2013-04-29 18:16       ` Yann Hodique

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=m2bo8yxyg2.fsf@jarvis.hodique.info \
    --to=yann.hodique@gmail.com \
    --cc=git@vger.kernel.org \
    /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.