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

Re: Git does not handle changing inode numbers well

From
Matthijs Kooijman <matthijs@stdin.nl>
Date
Aug 8, 2012, 18:07 UTC
Message-ID
<20120808180748.GS21274@login.drsnuggles.stderr.nl>
In-Reply-To
<20120808152230.GQ21274@login.drsnuggles.stderr.nl>
> So, let's see if I can fix my filesystem now ;-)

For anyone interested: turns out passing -o noforget makes fuse keep a persistent path -> inode mapping (at the cost of memory usage, of course).

However, it also turns out that fuse wasn't my problem: It was the aufs mount that was overlayed over my fuse mount (this was on a Debian live system), which sets the noxino option that prevents aufs from keeping persistent inode numbers.

To get git status working as expected, I had to both remove noxino from the aufs mount and add noforget to the underlying fuse mount.

Gr.
Matthijs
Previous: Matthijs Kooijman
Message 4 of 4 in “Git does not handle changing inode numbers well”
  1. Matthijs KooijmanAug 8, 2012
  2. Junio C HamanoAug 8, 2012
  3. Matthijs KooijmanAug 8, 2012
  4. Matthijs KooijmanAug 8, 2012

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.