I've got a vague itch to write a file system, for an academic exercise if nothing else, and I'm curious about what good filesystem design is all about. Particularly any properties that a filesystem design must have and/or should have to pass muster with the fs guys, and doubly particular how important these properties are. Besides the usual preemption safety/locking/smp awareness and all that stuff that's a given for kernel code in general, what are good principles to code for when you're designing a filesystem? In particular what I'm curious about includes but is by no means limited to the following: 1. POSIX compliance (given, probably trivial to research) 2. Integrity in the presence of catastrophic interruptions (crashes, kernel panics, power outages, random reboots) (I'm guessing a Good Thing) 3. Performance (given) 4. Robustness in the presence of flaky media (unsure how mandatory or required this is) 5. Anything I missed I'm intrigued by btrfs and tux3, and also a tad envious of the brains behind them. -- To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
