ZeroFS

Or just use https://github.com/Barre/ZeroFS Works pretty awesomely with git workloads, even Linux sized trees.

ZeroFS might help here to put the actual storage on an S3 compatible object store? https://github.com/Barre/zerofs

That’s a fair concern. The closest thing right now is a deterministic simulation suite that injects storage faults and crashes at arbitrary points, then checks the recovered data against reference models. It runs hourly with fresh seeds. CI also runs pjdfstest, xfstests, stress-ng, ZFS scrubs, and Jepsen crash/failover tests: https://github.com/Barre/ZeroFS#testing ZeroFS is still pretty young as storage projects go, so I completely understand wanting to see it prove itself over time.

Where is the "data loss window"? Between nodes or between the client and the infra? The front page lists under Capabilities: > 4.8 > Honest fsync > A successful fsync means every acknowledged write is durable in S3. If a failover may have lost unflushed writes, the next fsync returns an error instead of a false success. Someone else mentioned: "write() is buffered (that's the batching) and "committed" maps to fsync(), which returns only once data is durable." --- It sounds like all writes are written synchronously to at least one node but failovers/replicas are just eventually consistent. If so, latency between nodes is not within ZeroFS's control and including. Or are you saying that the latency is impossible for even a single node? If so, that would mean much more than just a footnote is needed. --- I don't see an issue with the benchma

Most of the pain here is the typical set of issues people run into trying to make S3 a filesystem as-is, common with S3FS-family approaches. ZeroFS (https://github.com/Barre/zerofs) is 9P/NFS/NBD over S3 on an LSM. Point stock go-git, or just /usr/bin/git, at a mount and skip the gymnastics. Rename is a metadata op in the keyspace, so you get it atomic on any S3, no Tigris-specific X-Tigris-Rename needed. Different point on the spectrum, but less square-peg, also most probably much, much faster (it works great on linux-sized repos) :)

Even with journaling, you might need one. ZeroFS [0] almost had a lost+found directory (even with the WAL enabled), because you might have consistency issues between your in-memory state and what was flushed, and especially in what order. ZeroFS ended up not needing recovery at all through atomic, strictly ordered commits [1], but it was far from trivial (and not just a matter of requiring a WAL). [0] https://github.com/Barre/ZeroFS [1] https://github.com/Barre/ZeroFS/blob/main/zerofs/src/fs/writ...

https://github.com/Barre/ZeroFS Should do a great job at this.

Or ZeroFS which doesn’t require a 3rd party database, just a s3 bucket! https://github.com/Barre/ZeroFS

SQLite works great with ZeroFS: https://github.com/Barre/ZeroFS

See also: https://github.com/Barre/ZeroFS

See also: https://github.com/Barre/ZeroFS Doesn’t require an external database (just a s3 bucket) and is a single binary. A webui is shipping in the next few days.

As of recently (workflows worked for months) I even have part of my CI on actions that fails with [0] 2026-02-27T10:11:51.1425380Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled. 2026-02-27T10:11:56.2331271Z ##[error]The operation was canceled. I had to disable the workflows. GitHub support response has been “ We recommend reviewing the specific job step this occurs at to identify any areas where you can lessen parallel operations and CPU/memory consumption at one time.” That plus other various issues makes me start to think about alternatives, and it would have never occurred to me one year back. [0] https://github.com/Barre/ZeroFS/actions/runs/22480743922/job...

I wonder how this compares to running sqlite off of an s3-backed ZeroFS https://github.com/Barre/ZeroFS

You might be interested in ZeroFS [0], it works great with Postgres [1]. To achieve what you describe, you should be just able to setup a Postgres replica that’s setup on top of ZeroFS. [0] https://github.com/Barre/ZeroFS [1] https://github.com/Barre/ZeroFS?tab=readme-ov-file#postgresq...

ZeroFS [0] is very thankful for what it brought to Linux with the v9fs [1] subsystem which is very nice to work with (network native) compared to fuse :) [0] https://github.com/Barre/ZeroFS [1] https://docs.kernel.org/filesystems/9p.html