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

Re: Committing crimes with NTFS-3G

From
RSRoman Sandu <r.sandu@gaijin.team>
Date
Aug 30, 2024, 19:25 UTC
Message-ID
<fe9d19fa-661d-4358-aa0a-ea419c419266@gaijin.team>
In-Reply-To
<ZtHe8Vi9aRmY-UMI@tapette.crustytoothpaste.net>
The stat output for a random file in the root of the repository is as 
follows:
```
   File: <CENSORED>
   Size: 91876     	Blocks: 184        IO Block: 4096   regular file
Device: 259,2	Inode: 4630629     Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 1000/romasandu)   Gid: ( 1000/romasandu)
Access: 2024-08-29 17:41:04.855126300 +0300
Modify: 2024-08-29 17:41:04.855609000 +0300
Change: 2024-08-29 17:41:04.855609000 +0300
  Birth: -
```
Maybe lack of a birth stat is what drives git crazy?
My git version is 2.43.0, which is the one from the Ubuntu 24.04 repo.

Neither `core.trustctime` nor `core.checkStat minimal` (nor a combination of them) help.

On 8/30/24 18:02, brian m. carlson wrote:
Show 22 quoted lines
> On 2024-08-30 at 12:52:05, Roman Sandu wrote:
>> Yes, I am aware that the index will be fully refreshed on the first run of
>> status. That is completely acceptable. But that is not what I am observing,
>> it is being refreshed on every single run of `git status`!
>>
>> After running stat before and after a status, the sha256 is identical. Both
>> for files and for folders. Maybe Windows has somehow corrupted the index
>> with its negative aura which makes git invalidate it on every single run?
>> Are there tools in git to diagnose the reason for the index's cache being
>> invalidated?
> 
> It would still be helpful to see the output of the `stat` command, since
> that would tell us useful things about what's causing Git to think the
> data has changed.  For example, some systems lack certain timestamp
> granularity, which can break Git when compiled in certain ways.
> 
> You can see if setting `core.trustctime` to false fixes it, and you can
> also try `core.checkStat` to `minimal` as well.  You should try them in
> that order to see if they fix things.
> 
> Also, what version of Git are you using?  Is it the one in Ubuntu 24.04,
> or the one from the git-core PPA, or a different one?
Previous: brian m. carlsonNext: brian m. carlson
Message 5 of 14 in “Committing crimes with NTFS-3G”
  1. Roman SanduAug 29, 2024
  2. brian m. carlsonAug 30, 2024
  3. Roman SanduAug 30, 2024
  4. brian m. carlsonAug 30, 2024
  5. Roman SanduAug 30, 2024
  6. brian m. carlsonAug 30, 2024
  7. Roman SanduAug 30, 2024
  8. Vito CaputoAug 30, 2024
  9. Johannes SixtAug 30, 2024
  10. Roman SanduAug 30, 2024
  11. Junio C HamanoAug 30, 2024
  12. Torsten BögershausenSep 3, 2024
  13. Roman SanduSep 3, 2024
  14. Torsten BögershausenSep 5, 2024

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.