| ▲ | pierrebarre 8 hours ago | |||||||
Author here. Thanks for posting this! It’s been quite a ride building ZeroFS, and I’m happy to answer any questions. | ||||||||
| ▲ | tandr 6 hours ago | parent | next [-] | |||||||
I'm thinking about using this and have a few questions:
Thank you! | ||||||||
| ▲ | the_duke 5 hours ago | parent | prev | next [-] | |||||||
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) | ||||||||
| ▲ | chillfox 7 hours ago | parent | prev | next [-] | |||||||
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? | ||||||||
| ||||||||
| ▲ | nubg 4 hours ago | parent | prev [-] | |||||||
This blog post seems to have been written by an AI based on a prompt you gave it? Can you confirm or deny this? | ||||||||