Linked by Thom Holwerda on Sat 18th Nov 2006 18:20 UTC, submitted by bnolsen
Linux "SpadFS is a new filesystem that I design and develop as my PhD thesis. It is an attempt to bring features of advanced filesystems (crash recovery, fast directories) and good performance without increasing code complexity too much. Uses crash counts instead of journaling (because journaling is too complex and bug-prone) and uses hash instead of btrees for directory organization."
Thread beginning with comment 184128
To view parent comment, click here.
To read all comments associated with this story, please click here.
bnolsen
Member since:
2006-01-06

This is pretty funny.

Databases are a higher level paradigm than filesystems. As mentioned above, you need to put a database onto a filesystem to make it useful. Then of course you end up with more overhead.

BeOS tried a database fs orignally and ended up ditching it for a more traditional filesystem. MS played with it for Longhorn and ditched the idea also.

Layers of building blocks work better than monolithic giants. They're easier to implement, test and keep stable.

What I like most about the spad filesystem is the codebase size. Currently it's LOC count is even less than ext2. Generally more elegant solutions end up being smaller.

Edited 2006-11-21 15:37

Reply Parent Score: 1

axilmar Member since:
2006-03-20

the only thing databases require are a block device. They do not need a filesystem. Memory-driven databases are a testament to that.

The relational model is far superior than the simple byte-oriented unstructured model of files.

Reply Parent Score: 1