As I see it, there are no SSD devices which don't lose data; there
are only SSD devices which haven't lost your data _yet_.
-- David Woodhouse
What I've been recommending for some time is that people use LVM, and
run fsck on a snapshot every week or two, at some convenient time when
the system load is at a minimum. There is an e2croncheck script in
the e2fsprogs sources, in the contrib directory; it's short enough
that I'll attach here here.
Is it *necessary*? In a world where hardware is perfect, no. In a
world where people don't bother buying ECC memory because it's 10%
more expensive, and PC builders use the cheapest possible parts --- I
think it's a really good idea.
-- Ted Ts'o
What it basically shows is how intolerant the mainline kernel
community members have become towards people who hold a different
view to them. The attitude is: either conform or you're an idiot
and we're going to attack you until you conform.
I do hope others see what has happened here, and seriously consider
whether they want to get involved in a sniping dictatorial
community. Maybe considering to go down the BSD route instead.
-- Russell King
Because it throws out everything about what we know is good about how to
design a modern scheduler in scalability.
Because it's so ridiculously simple.
Because it performs so ridiculously well on what it's good at despite being
Because it's designed in such a way that mainline would never be interested
in adopting it, which is how I like it.
Because it will make people sit up and take notice of where the problems are
in the current design.
Because it throws out the philosophy that one scheduler fits all and shows
that you can do a -lot- better with a scheduler designed for a particular
purpose. I don't want to use a steamroller to crack nuts.
-- Con Kolivas
to post comments)