Linked by Thom Holwerda on Sat 24th Feb 2007 21:25 UTC, submitted by mdoverkil
BSD and Darwin derivatives Apparently, Matt Dillion has decided to roll his own filesystem for DragonFly. "Here is my initial outline of the filesystem design. It is open for discussion. Please feel to ask questions for anything you do not understand. I do not intend to start coding anything for at least two weeks. There are currently two rough spots in the design. First, how to handle segment overflows in a multi-master environment. Such overflows can occur when the individual masters or slaves have different historical data retention policies. Second, where to store the regeneratable indexes."
Thread beginning with comment 216422
To read all comments associated with this story, please click here.
there are lots of interesting ideas here
by daveiler on Sun 25th Feb 2007 17:31 UTC
Member since:

I don't know about the innards of every filesystem ever written, but there are some really neat ideas here.

* Inherent snapshots (versions of every file are saved until space is needed)
* Distributed records. (all information for the files are stored in a segment near the file) which means the master records can be recovered from scratch by reading the disk
* Other cool things

I say bravo for coming up with novel ideas, and I can't wait to see how it performs.

And I haven't even reached the end of the document...

Reply Score: 1