git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Tso <tytso@mit.edu>, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [BUG ext4?] Working tree getting out of date "spontaneously"
Date: Fri, 5 Jun 2009 18:14:44 +0200	[thread overview]
Message-ID: <20090605161444.GD764@atjola.homenet> (raw)
In-Reply-To: <alpine.LFD.2.01.0906050825120.6847@localhost.localdomain>

On 2009.06.05 08:39:24 -0700, Linus Torvalds wrote:
> 
> 
> On Fri, 5 Jun 2009, Björn Steinbrink wrote:
> > > 
> > > *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:
> 
> You have beagle running, don't you?

No, nothing like that is running here, I even switched to runlevel 1
just to make sure ;-)

> It's a piece of sh*t, and uses extended attributes to track indexing 
> information.
> 
> So the "wait a minute" will just give beagle the chance to index your git 
> working tree, and update the extended attributes. That is entirely hidden 
> from all normal filesystem stat information, *EXCEPT* it changes ctime, 
> since the inode is changed.

No, I'm pretty sure now that it's due to the fact that I use the ext4
kernel driver with an ext3 fs, as running sync(1) is as good as waiting
a minute. And the problem shows up neither with tmpfs nor with a real
ext4.

Björn

      reply	other threads:[~2009-06-05 16:14 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
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 [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090605161444.GD764@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).