[ECOS] FW: Mount JFFS2 root file system issue

[Gary Thomas]

Lin, Bin (Bin) wrote:
> Hi Gary,
> 
> Thanks a lot for your reply. 
> 
> It is understandable that JFFS2 needs to rebuild/recover the active
> nodes in the next reboot after failure.  But once this happen, every
> reboot later on will take the same amount of time which is much long
> than normal. I have to re-program the entire flash to get it back to
> normal mount time. 
> 
> Also this problem can not reproduced in the lab. Is there a way to
> craete this problem quickly?

No clue, sorry.

As I said, since this isn't an eCos issue, you should ask the JFFS2
folks (linux-mtd@lists.infradead.org) or Linux mailing lists.

> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com] 
> Sent: Friday, January 11, 2008 7:40 AM
> To: Lin, Bin (Bin)
> Cc: ecos-discuss@sourceware.org
> Subject: Re: [ECOS] FW: Mount JFFS2 root file system issue
> 
> Lin, Bin (Bin) wrote:
>> Hello All,
>>
>> I have ARM9 systems with JFFS2 root file system. For some reasons,
> e.g.
>> system crash or power failure, when system boots up next time, it 
>> takes much longer time than usual to mount jffs2 root file system. It 
>> can hang at following message for 3-10 min. The system will eventually
> 
>> come up and function well. This problem occurred on less than 10% of
> boards.
> 
> I think this can happen (after such a failure) when JFFS2 realizes that
> it needs to rebuild/recover the active nodes in the file system.  This
> can require a scan of the entire file system, along with rewriting some
> nodes, etc.
> 
>> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>> Fast Floating Point Emulator V0.9 (c) Peter Teichmann.
>>
>> There are some symbolic links in the root file system. These links is 
>> linked to the files in another partition. Could that cause problem if 
>> the file in the other partition gets corrupted? This behaviour is not 
>> reproducible. Looks like the files in the flash are not corrupted. I 
>> guess the corruption could be in jffs2 file system.
>>
>> Anyone has seen this issue, and solution?
>>
>> Appreciate very much for any input,
> 
> This looks to be a Linux kernel issue - I don't see what it has to do
> with eCos.
> 
> You should probably ask on some appropriate Linux mailing list.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss