[OT] I'm testing/developing (the latter mostly on hardware side) many things, that results in device shutting down not-nice way. Most of the times, recovering journal for a file system is enough, but often, something else is broken and fsck attempts to repair it.

Here comes a problem - all ext* fsck tools just doesn't work well for flash, if anything above journal recovery is needed. It gets confused, and attempt by fsck to repair even a minor glitch, results in making filesystem a total FUBAR.

Thats why I disabled all automatic fsck tests, and after every bad shutdown, I do fsck manually, from recovery shell. If recovering journal isn't enough, I create a backupmenu backup (which just skip broken files on read errors - of course I keep track on what got lost), then re-create filesystem from scratch on given partition, and restore backup.

AFAIK, it's the only way to have a healthy filesystem in case of something getting ugly. Regular fsck routines are of no use for us. [/OT]

/Estel