From: shentino <shentino@gmail.com>
To: linux-newbie@vger.kernel.org
Subject: What makes a good filesystem?
Date: Mon, 01 Jun 2009 12:15:34 -0700 [thread overview]
Message-ID: <1243883734.3835.10.camel@avalar> (raw)
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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
reply other threads:[~2009-06-01 19:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1243883734.3835.10.camel@avalar \
--to=shentino@gmail.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox