I'm thinking about using this and have a few questions:

    1. How are hardlinks and duplicate files (same content, different paths) handled?
    2. Does deduplication work on a block/chunk level for partially matching files, or does it only look at whole files?
    3. Is there any specific integration or handling for Copy-on-Write (CoW)?

I was investigating the design a little. Two big questions:

A) You notably don't write a recovery log (WAL/journal) for things not yet flushed, so data can be lost. Do you have plans to add this? I think it would be pretty crucial.

B) the system is single writer. Do you have plans for adding horizontal scalability so a writer can be dynamically selected and routed to, transparent to the client? (Or with client cooperation, but without forcing sharding on the user)

Thanks for building this, I am just about to give it ago with my self-hosted Garage cluster.

Does running `stat` against a file require pulling the whole file from s3, or can that be handled by the metadata?

Do you know what backup performance is like for something like borg/borgmatic or restic, especially on follow up runs where most files are just checked.

Is there any particular Redis/Valkey config you recommend when using it for `conditional_put`, or just default config?

Is there any chance for NFSv4 support?

This blog post seems to have been written by an AI based on a prompt you gave it? Can you confirm or deny this?