Re: [PATCH 2/7] core.fsyncmethod: batched disk flushes for loose-objects

From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Mar 16, 2022, 11:50 UTC
Message-ID: <65998787-15e4-fac4-1343-65df60e971d0@gmail.com>
In-Reply-To: <d38f20b4430bada1d0dccc1e600e6f0b098f3767.1647379859.git.gitgitgadget@gmail.com>

On 16/03/22 04.30, Neeraj Singh via GitGitGadget wrote:

Show 6 quoted lines

> On a filesystem with a singular journal that is updated during name
> operations (e.g. create, link, rename, etc), such as NTFS, HFS+, or XFS
> we would expect the fsync to trigger a journal writeout so that this
> sequence is enough to ensure that the user's data is durable by the time
> the git command returns.
>

But what about ext4? Will fsync-ing trigger writing journal?

-- 
An old man doll... just what I always wanted! - Clara

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