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

Re: Multiple clients accessing git over NFS

From
GTGreg Troxel <gdt@ir.bbn.com>
Date
Nov 14, 2010, 23:46 UTC
Message-ID
<rmipqu7lb8f.fsf@fnord.ir.bbn.com>
In-Reply-To
<AANLkTinX-XR2TaZPGPeWyekMq3e8wEDkfcmi_o6pTvMK@mail.gmail.com>

If only one computer is accessing the repository, then failure to lock may be ok. But you'll still need atomic rename etc. to work.

I may be overly conservative, but I would not (and do not) allow anyone to access a repository (cvs, svn, git, whatever) over NFS, ever.

My expectation is that multiple git processes on one machine with a repo on local disk works fine. If not it's a bug. When you add a remote FS you have to wonder if the unix filesystem sematics are preserved.

Another approach would be cloned repositories that constantly pull from the main one or each other, and have people use those. That will get you delayed merge conflicts, but they might be useful as RO replicas.

Previous: Alex
Message 10 of 10 in “Multiple clients accessing git over NFS”
  1. Khawaja ShamsNov 14, 2010
  2. Greg TroxelNov 14, 2010
  3. Khawaja ShamsNov 14, 2010
  4. Jonathan NiederNov 15, 2010
  5. Jan HudecNov 15, 2010
  6. Drew NorthupNov 15, 2010
  7. J. Bruce FieldsNov 15, 2010
  8. Sitaram ChamartyNov 15, 2010
  9. AlexNov 16, 2010
  10. Greg TroxelNov 14, 2010

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.