From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Theodore Tso <tytso@mit.edu>
Cc: Junio C Hamano <gitster@pobox.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
git@vger.kernel.org
Subject: Re: [BUG ext4?] Working tree getting out of date "spontaneously"
Date: Fri, 5 Jun 2009 16:12:09 +0200 [thread overview]
Message-ID: <20090605141209.GA764@atjola.homenet> (raw)
In-Reply-To: <20090605132126.GB11035@atjola.homenet>
On 2009.06.05 15:21:26 +0200, Björn Steinbrink wrote:
> On 2009.06.05 14:24:44 +0200, Björn Steinbrink wrote:
> > Hi,
> >
> > can't make any sense out of this at all:
> >
> > doener@atjola:git (master) $ git reset --hard HEAD@{1}
> > HEAD is now at b11cf09 Merge branch 'da/pretty-tempname'
> > doener@atjola:git (master) $ git update-ref refs/remotes/origin/master HEAD
> >
> > doener@atjola:git (master) $ git pull
> > >From git://git.kernel.org/pub/scm/git/git
> > b11cf09..6096d75 master -> origin/master
> > Updating b11cf09..6096d75
> > Fast forward
> > Documentation/RelNotes-1.6.3.2.txt | 12 +++++-------
> > Documentation/git.txt | 7 ++++++-
> > contrib/completion/git-completion.bash | 12 ++++++++++--
> > grep.c | 6 +++++-
> > 4 files changed, 26 insertions(+), 11 deletions(-)
> >
> > doener@atjola:git (master) $ git diff-index --name-only HEAD
> > doener@atjola:git (master) $ git diff-index --name-only --cached HEAD
> >
> > *wait a minute, doing nothing*
> >
> > doener@atjola:git (master) $ git diff-index --name-only HEAD
> > Documentation/RelNotes-1.6.3.2.txt
> > Documentation/git.txt
> > contrib/completion/git-completion.bash
> > grep.c
>
> Hm, looks like this is not a git bug. Went back to 1.5.4, and even that
> shows the error. So I actually looked at the files, and indeed, the file
> in the working tree gets modified. stat(1) shows:
>
> Right after the merge:
> File: `grep.c'
> Size: 16274 Blocks: 32 IO Block: 4096 regular file
> Device: fd03h/64771d Inode: 5933481 Links: 1
> Access: (0644/-rw-r--r--) Uid: ( 1000/ doener) Gid: ( 1000/ doener)
> Access: 2009-06-05 15:02:14.000000000 +0200
> Modify: 2009-06-05 15:02:14.000000000 +0200
> Change: 2009-06-05 15:02:14.000000000 +0200
>
> 60 seconds later:
> File: `grep.c'
> Size: 16274 Blocks: 32 IO Block: 4096 regular file
> Device: fd03h/64771d Inode: 5933481 Links: 1
> Access: (0644/-rw-r--r--) Uid: ( 1000/ doener) Gid: ( 1000/ doener)
> Access: 2009-06-05 15:02:14.000000000 +0200
> Modify: 2009-06-05 15:02:14.000000000 +0200
> Change: 2009-06-05 15:02:48.000000000 +0200
>
> So the ctime got modified. I don't have any fancy indexing stuff
> running, and inotify doesn't see any events either while the ctime is
> changed.
>
> The only thing I changed lately was upgrading to 2.6.30-rc8 and going
> from ext3 to ext4. As the ctime change always seems to happen around 30
> seconds after the real change, I kind of suspect ext4 to be guilty.
> Ted, is that possible?
>
> FS is mounted as:
> /dev/mapper/vg0-home on /home type ext4 (rw,noatime,nodiratime,barrier=0)
Hm, yup, seems to be ext4 related, doesn't happen on tmpfs.
Björn
next prev parent reply other threads:[~2009-06-05 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 12:24 [BUG?] Working tree getting out of date "spontaneously" Björn Steinbrink
2009-06-05 13:14 ` Robin Rosenberg
2009-06-05 13:23 ` Björn Steinbrink
2009-06-05 13:21 ` [BUG ext4?] " Björn Steinbrink
2009-06-05 14:12 ` Björn Steinbrink [this message]
2009-06-05 14:47 ` [BUG? ext4] git working " Björn Steinbrink
2009-06-05 14:55 ` [BUG ext4?] Working " Theodore Tso
2009-06-05 15:02 ` Björn Steinbrink
2009-06-05 18:06 ` Theodore Tso
2009-06-05 18:35 ` Björn Steinbrink
2009-06-05 21:38 ` Theodore Tso
2009-06-05 15:39 ` Linus Torvalds
2009-06-05 16:14 ` Björn Steinbrink
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=20090605141209.GA764@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@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.
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 NNTP newsgroup(s).