UBIFS Corrupt during power failure
Artem Bityutskiy
dedekind at infradead.org
Fri Apr 10 13:11:40 EDT 2009
On Fri, 2009-04-10 at 11:00 -0600, Eric Holmberg wrote:
> Thank you very much for your help so far.
NP, this is all I can do now without having real NOR and
much time :-)
> I am going to do two things:
> 1. Turn off write buffering which converts the NOR minimum I/O size from 1 to effectively 32 16-bit words (64 bytes) and re-run all of the tests.
Err, which buffering? Is this something at the flash driver
level?
Note, UBIFS never talks to MTD level, it talks only
to UBI level, which talks to MTD. UBI will provide UBIFS
min. I/O unit size which it reads from mtd->writesize.
Then if it is < 8, UBIFS will use 8 instead. There is not
fundamental reason for this, it was just easier to implement
UBIFS this way. But this is not big deal.
In your case, as I see from your logs, min. I/O unit reported
from MTD to UBI is 1, and from UBI to UBIFS it is 1, but then
UBIFS will use 8 instead. This means all write commands UBIFS
will issue will be aligned to 8 and be multiple of 8.
So if you are talking about turning off some buffering on
MTD level, may be it is ok. But if you are talking about
UBIFS level - no need to do anything there.
> 2. While this is running, I'm going to start following the modifications and debugging path that you outlined.
>
> I'll report back with findings and potential modifications -- as always, feel free to ping me if you don't hear anything!
OK.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
More information about the linux-mtd
mailing list