Hi,
> lost+found). Short of going to a journaling file system, are
> there any
> other methods that anyone can recommend? (And no, I don't
> have control of
> the hardware so I can't prevent an unexpected shutdown.)
I think of two solutions that could help:
- Mount your partition read only and install a ramdisk for logs etc.
- use initrd to run linux completely in ram
I made experiments with reiserfs because I've got the same problem here. But
I learned that also a journaling fs may become corrupt when power fails (the
same with ntfs and embedded nt.)
One suggestion to the cracks: what about a kind of 'write filter' as it is
used with embedded nt? Read data come from the flash/hd and when tried to
write a file, this file is stored in ram instead of the flash/hd. Subsequent
reads to that file go to the ram-copy. This leaves the system always in the
same state when powering up but enables to work on it as if there's a
writable flash/hd available. No write accesses to flashs, therefore no
corrupted fs when suddenly powered down. Capable of running a system from a
read-only device (CDROM...). Beside, one doesn't need to hold the whole
root-fs in ram as it is done with initrd.
Jürgen Striegel
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
