git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: consistency problem on ZFS

From
Yann Hodique <yann.hodique@gmail.com>
Date
Apr 28, 2013, 20:21 UTC
Message-ID
<m2zjwiwgng.fsf@jarvis.hodique.info>
In-Reply-To
<CAEBDL5W8E_i3V1ePWkf0Ep2iTjY59abqU7Q2w4o0iA8=P_4Onw@mail.gmail.com>
>>>>> "John" == John Szakmeister <john@szakmeister.net> writes:
Show 16 quoted lines
> 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
Previous: John SzakmeisterNext: Junio C Hamano
Message 5 of 9 in “consistency problem on ZFS”
  1. Yann HodiqueApr 28, 2013
  2. Thomas RastApr 28, 2013
  3. Yann HodiqueApr 28, 2013
  4. John SzakmeisterApr 28, 2013
  5. Yann HodiqueApr 28, 2013
  6. Junio C HamanoApr 28, 2013
  7. Yann HodiqueApr 29, 2013
  8. Junio C HamanoApr 29, 2013
  9. Yann HodiqueApr 29, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.