Re: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste

From: Linus Torvalds <torvalds@osdl.org>
Date: May 22, 2005, 19:09 UTC
Message-ID: <Pine.LNX.4.58.0505221205580.2307@ppc970.osdl.org>
In-Reply-To: <20050522122849.GJ15178@cip.informatik.uni-erlangen.de>

On Sun, 22 May 2005, Thomas Glanzmann wrote:

>
> I wonder why 'git-update-cache --refresh' running in the same directory
> shared via NFS ends up in reindexing the whole files when running on
> different machines on a NFS share.

It does?

Can you check what

	ls -li --time=atime

shows on the different clients? Also, try "ctime".

> Is there a reason for this or can it easily be fixes. I also wonder if
> the locking which is used to lock the cache is 'nfs safe'.

It _should_ be safe. It does the old lockfile thing, with a "link()" that should guarantee atomicity. No fcntl locking or similar that can have problems with networked filesystems and different UNIXes.

		Linus