Linked by Thom Holwerda on Sun 14th Oct 2007 14:52 UTC, submitted by Oliver
Matthew Dillon writes: "I am going to start committing bits and pieces of the HAMMER filesystem over the next two months. Note that the filesystem will not be operational until we get closer to the 2.0 release in December so these bits and pieces will not be tied into buildworld/buildkernel until then." Features: maximum size of half an exabyte, infinite snapshots, limited only by retention policy, streaming backups, asynchronous transactional support (no long fscks to check disk state). Dillon also explains why he chose not to use Sun's ZFS.
Permalink for comment 278139
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-07
On face value you might appear to be correct, but you have forgotten an important point. Matt is sitting in a very unique position when it comes to implementing this. He has free access to make the changes necessary in any part of the system he needs without much worry of requiring or maintaining backwards compatibility. Make no mistake, that can make all the difference when it comes to implementing such deep-rooted technologies quickly.
I also believe that this type of "filesystem" (I put quotes because this level of functionality goes far beyond a typical filesystem) has been his goal since the inception of DragonFlyBSD so all of the work to date has been done to facilitate the addition of HAMMER.