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 216219
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why?
by galvanash on Sat 24th Feb 2007 22:28 UTC in reply to "Why?"
galvanash
Member since:
2006-01-25

Ill be honest up front... I have never used Dragonfly nor do I have any intention to at the moment, but I have been interested enough in it to read up on its status now and again. And I find your remarks somewhat puzzling.

Dragonfly started in 2003 (4 years ago). The goal was to (a) take FreeBSD and implement what the developers felt was a more sensible approach to SMP support with the purpose of laying the foundation for... (b) native clustering. That has been the stated goal since day 1.

(a) is pretty much done now, and (b) is more or less dependent on a new file system according to everything I have read about their clustering approach. How you think this is getting sidetracked I don't quite follow...

Edited 2007-02-24 22:40

Reply Parent Score: 5