Re: kernel messages from INFTL

Andre
2005-07-06T16:59:07Z

[snip]
>>>> INFTL: formatting chain at block 24574
>>>> INFTL: formatting block 24574
>>>> INFTL: corrupt block 24575 in chain 24575, chain length 0, erase
>>>> mark 0xffff?
>>>> INFTL: formatting chain at block 24575
>>>> INFTL: formatting block 24575
>>>> inftla: inftla1
>>>> ==================
>>>> The INFTL messages do not appear on subsequent loads of the inftl
>>>> module. Can somebody please explain what happened, i.e. should I be
>>>> concerned?
>>>
>>> The INFTL code is telling you that it didn't think the chains
>>> where logically correct. So it went ahead and tried to fix them up.
>>> Once fixed you should not see any messages on the next boot (as
>>> you didn't). Certainly not normal (or good).
>>
>>
>> The device really started to act up on subsequent boot and I
>> couldn't even format it anymore with m-sys tools. The dformat
>> utility complained about not being able to find the bad block table.
>
> My best guess is that the bad block info is stored differently than
> what the current INFTL code can deal with then. I have only used it
> on the Disk-on-chip Millenium+ parts, and the bad block table is
> stored in the factory reserved region on those parts (which I believe
> is different to their other DoC parts).

here is a link to somebody else that is using the exact same part, although
he is experiencing different problems:
http://thread.gmane.org/gmane.linux.drivers.mtd/12814

Can you tell from this where the bad block table is stored?

> Can you fully restore it with the M-systems tools?

no, format wouldn't work anymore and I couldn't boot the system with the DoC
installed because of some corruption in the boot sector - the BIOS would
complain and would hang, so I decided to send it back to the supplier for
replacement.

>
> You will need to debug the INFTL init logic and figure out what how
> the initial block layout is different.

There is just one thing I would like to know: starting with an m-sys
formatted device, does linux-mtd touch anything on the device during the
inftl mount? The inftl debug messages seem to indicate that certain
'formatting' operations are taking place. Maybe I am overly protective, but
shouldn't 'mount' be a read-only operation?