25 Sep
2008
25 Sep
'08
3:13 p.m.
Alexander Schreiber wrote:
What most journaled file systems gain
you is that you don't need to spend 20 min in fsck after a powerfailure
... or after n reboots, where n is designed to fall at the moment of maximum
incovenience... :-)
just less than a minute in journal rollback.
I tend to run ext3 on any linux system of mine, which seems to do a very good
job at not disappearing up its own backside. I did try reiserfs for a while
until the whole filesystem on my development system decided to eat itself -
never again.
Running a journaled FS on top of flash _greatly_
hastens the demise of
your flash, because of the massive amount (compared to the rest of the
flash) of write traffic the flash blocks in the journal will get. Even
wear leveling can only mitigate that effect so much.
Although at least with ext3 - and probably other journaled filesystems - you
can specify that the journal resides on a completely different device. How
useful that is in practice, I'm not sure - but you don't *have* to have the
journal stored on the same device as the associated data.
Before I left the UK, I'd replaced the IDE drive in my main data recovery
system with a CF card (a lowly 32MB, too, as data was all stored remotely via
the network), but unfortunately I didn't get chance to really hammer the card
before I left, and it might be a while before the machine catches up with me...
cheers
Jules