Your best bet is to not use the file system type that they tell you to use on the MMC card.  You need to use JFFS2 or one of the other journalling file systems. They are designed to be recovered in those sorts of situations.  When you loose power in the midle of a file write, the only mitigation with the current file system is to panic, or run an fsck on the file system when it comes up.  All that will do though is put the inodes used in the corrupted file write into lost+found for that partition.

So instead, you probably want to use jffs or jffs2 or.. whichever others are out there.


On Wed, Aug 26, 2009 at 8:53 AM, rketcham <> wrote:

Hi Everyone,

I've noticed that when the gumstix (Verdex Pro XL6P) gets shutdown
unexpectedly while a file is being written to, and is consequently
corrupted, one of two things seem to happen on reboot:

1. The mmc card mounts fine but when the corrupted file is accessed the
system panics and remounts the card as read-only.


2. The mmc card is mounted read-only.

My question is what can I do to mitigate this? The best solution would be to
keep the file from being corrupted in the first place but if that can't be
done, is there a way to identify the corrupted file and remove it without
causing the system to remount the card as read only?

So, far the only thing that I've found to work is to format the card when
the card suddenly becomes read-only and a remount doesn't solve the problem
but this potentially destroys data that I may need.

Thank you for your suggestions.

View this message in context:
Sent from the Gumstix mailing list archive at

Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
gumstix-users mailing list

Say you can or say you can't, either way you will be right.
Computers are like old testament gods: Lots of rules and no mercy.