From: Yann Hodique <yann.hodique@gmail.com>
To: git@vger.kernel.org
Subject: Re: consistency problem on ZFS
Date: Sun, 28 Apr 2013 21:21:07 +0100 [thread overview]
Message-ID: <m2zjwiwgng.fsf@jarvis.hodique.info> (raw)
In-Reply-To: CAEBDL5W8E_i3V1ePWkf0Ep2iTjY59abqU7Q2w4o0iA8=P_4Onw@mail.gmail.com
>>>>> "John" == John Szakmeister <john@szakmeister.net> writes:
> On Sun, Apr 28, 2013 at 3:11 PM, Yann Hodique <yann.hodique@gmail.com> wrote:
>> 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'
>> $
> Since you're running with Mac OS X, can I ask what version? Have you
> seen this with the regular file system (HFS) at all? It might be that
> you need to disable core.trustctime.
Sure, it's OS X 10.8.3
And no, I don't see this on HFS+ at all. I've just tried numerous times
without success.
And setting core.trustctime seems to do the trick indeed. Many thanks,
that's helping a lot in the short term !
Yann.
--
At the age of fifteen, he had already learned silence.
-- from "A Child's History of Muad'Dib" by the Princess Irulan
next prev parent reply other threads:[~2013-04-28 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 19:11 consistency problem on ZFS Yann Hodique
2013-04-28 19:33 ` Thomas Rast
2013-04-28 19:44 ` Yann Hodique
2013-04-28 20:12 ` John Szakmeister
2013-04-28 20:21 ` Yann Hodique [this message]
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=m2zjwiwgng.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.