I don’t get why they went for NFSv3, v4 is quite old and I can’t think of any reason why you would choose v3 over v4.
Because it’s harder. It’s a stateful protocol and has a lot more features
Show HN: ZeroFS – A log-structured filesystem for S3
41–50 of 60 posts
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#42> The test suites run in public CI. > Each card links to the CI pipeline. Thanks for being explicit, AI written marketing site. Wouldn't have been able to figure that out! Every currently maintained and reasonably popular open source project either runs CI in public or makes the tests extremely easy to run.
I got the same vibe from > These are asciinema recordings of real terminal sessions, rendered as text rather than video. Playback caps idle pauses at two seconds and changes nothing else. Thanks? This sounds like it's the LLM's response to the prompter, not something you should display on the page itself...
I see this all the time in code reviews at work. Extremely verbose comments that teach the clueless author how things work but have no place in the final code: aside from codebase not being a coding tutorial, they are also incredibly specific and would become stale and incorrect in matter of weeks.
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#43That name makes it sound like your files end up in /dev/null.
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#44So, can I run this on top of RustFS? And RustFS on top of this?
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#45So, can I run this on top of RustFS? And RustFS on top of this?
Kind-of should work :)
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#46Why does this landing page load js from merklemap.com?
The page doesn’t load anything for me… I block JS by default, & something that should be informational is hiding it’s content behind scripts for some reason.
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#47I prototyped something like this for fun a long time ago. Treating s3 like a bucket of blocks seemed intuitive way build a scalable filesystem. Arguably ceph and luster are doing something similar except with a seperate metadata servers to serve the hotter content.
I think the critical thing you will need to explain is durability and loss window. Making some guarentees on failure modes would go a long way towards making me believe i can run operations on something like this.
With AI you should be able to do some exhaustive testing both for load, power loss, server loss, etc. Anxious to see the potential results
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#48I believe the first version of this required the metadata to be stored on the ZeroFS server, making HA kinda hard. This has changed now that if I stop the server and create a new instance with the same configuration file it'll pickup the existing metadata from the bucket?
> I believe the first version of this required the metadata to be stored on the ZeroFS server, making HA kinda hard. Metadata has always been in the bucket itself. For HA, there's now a "replicated mode" if you want automatic failover: https://www.zerofs.net/docs/high-availability
The HA certainly makes this more of an alternative to JuiceFS now.
Would need something like HAProxy to correctly handle failover for NFS though?
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#49Worth mentioning FiberFS: https://fiberfs.io/
I believe it just recently launched.
Re: Show HN: ZeroFS – A log-structured filesystem for S3
#50previous Show HNs
- https://news.ycombinator.com/item?id=48496242 -- 11 points | 20 days ago | 7 comments
- https://news.ycombinator.com/item?id=45174724 -- 64 points | 9 months ago | 40 comments
blog post 3 days ago: https://news.ycombinator.com/item?id=48712122