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
On Sun, Apr 28, 2013 at 3:11 PM, Yann Hodique [off-list ref] 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.
-John
PS Sorry for the repeat Yann... I forgot to CC the list.
quoted
quoted
quoted
quoted
"John" == John Szakmeister [off-list ref] writes:
On Sun, Apr 28, 2013 at 3:11 PM, Yann Hodique [off-list ref] wrote:
quoted
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