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

Re: warning: ignoring unknown core.fsync component 'true'

From
Patrick Steinhardt <ps@pks.im>
Date
Jul 23, 2025, 05:27 UTC
Message-ID
<aIBy3xH2eZsCZYiY@pks.im>
In-Reply-To
<209ecbf7-0d53-4674-bb7b-3ca084edb761@windriver.com>
Hi Jinfeng,
On Wed, Jul 23, 2025 at 11:07:37AM +0800, Wang, Jinfeng (CN) wrote:
Show 10 quoted lines
> For a specific git repo, when I clone or fetch the repo, I encounters the
> warning
> 
> remote: warning: ignoring unknown core.fsync component 'true'
> remote: Enumerating objects: 41, done.
> remote: Total 41 (delta 0), reused 0 (delta 0), pack-reused 41
> Unpacking objects: 100% (41/41), 37.51 MiB | 10.91 MiB/s, done.
> 
> But after clone the repo, I didn't see core.fsync in my .git/config. And
> there isn't anything relates core.fsync.

The problem doesn't exist on the client-side, but rather on the remote as indicated by the "remote: " prefix. So there's nothing you can do on the client-side to address the problem, you'll have to reach out to the admin of that repository and tell them that the repository uses an invalid value for "core.fsync".

> I also tried git with different version (2.25.1 and 2.34.1) to clone the
> repo, both will show this warning. What configuration causes this warning?

It's "core.fsync" indeed, but not on your side. The config does not take a boolean, but rather a list of components that should use fsync. I guess the admin wanted to just fsync everything, but in that case you don't want "core.fsync=true" but "core.fsync=all".

Patrick
Previous: Wang, Jinfeng (CN)Next: Wang, Jinfeng (CN)
Message 2 of 3 in “warning: ignoring unknown core.fsync component 'true'”
  1. Wang, Jinfeng (CN)Jul 23, 2025
  2. Patrick SteinhardtJul 23, 2025
  3. Wang, Jinfeng (CN)Jul 24, 2025

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.