Pierre Menard, author of The Filesystem.<p>But I'm surprised this is possible without a specification - how can you test a filesystem through hexdumps? The effects of some operations are going to pretty far-reaching, surely?
Does someone know whether it would be legal for someone to go through the ZFS code and write a specification of the features this author hasn’t figured out yet? I.e. could someone write a detailed description of the missing functionality that doesn’t include any details about the implementation so other people can implement it in non-CDDL code?
What?! How?! Why?!<p>This is the greatest thing ever.
I wish I could just write code for the fun of it. Every time I wonder whether people will use it and give up before I even get started.
i love userspace implementations of filesystems.<p>note that the issues are entirely different from those with a kernel implementation since you aren't having to think about page cache et all.
Hey alcari!<p>I know you from ICV - we used to hang out online on the forums and IRC.<p>Nice work on this project, I'm looking forward to diving into the codebase!
There's also TFS a ZFS inspired FS in Rust <a href="https://github.com/redox-os/tfs" rel="nofollow">https://github.com/redox-os/tfs</a>
Simultaneously fucking awesome (that you pulled it off at all), and fucking useless (performance...).<p>Thanks for sharing though. Maybe could be useful in making a suite of zfs inspection tools?<p>Is the OP here? How difficult would it be creat a zfs reshaping tool, allowing for the offline expansion of a vdev?