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

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

From
TGThomas Glanzmann <sithglan@stud.uni-erlangen.de>
Date
May 22, 2005, 12:28 UTC
Message-ID
<20050522122849.GJ15178@cip.informatik.uni-erlangen.de>

Hello, 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.

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'.

	Thomas
Next: Linus Torvalds
Message 1 of 8 in “running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste”
  1. Thomas GlanzmannMay 22, 2005
  2. Linus TorvaldsMay 22, 2005
  3. Thomas GlanzmannMay 22, 2005
  4. Linus TorvaldsMay 22, 2005
  5. Don't include devicenumber into INODE_CHANGED test [WAS: Re: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste]Thomas Glanzmann, May 22, 2005
  6. Alternate Patch: [PATCH] Don't include device number in cache invalidation when running on NFSThomas Glanzmann, May 22, 2005
  7. Linus TorvaldsMay 22, 2005
  8. Thomas GlanzmannMay 22, 2005

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.