ts-7000
[Top] [All Lists]

[ts-7000] Puzzling JFFS2 warning

To:
Subject: [ts-7000] Puzzling JFFS2 warning
From: Andrew Gaylard <>
Date: Sun, 25 Jun 2006 18:03:27 +0200
Hi all,

I've recently encountered this warning when booting my TS7200:
(apologies for the long lines)

JFFS2 error: (297) jffs2_build_inode_pass1: child dir "run" (ino #790)
of dir ino #15 appears to be a hard
link                                               
JFFS2 error: (297) jffs2_build_inode_pass1: child dir "spool" (ino #791)
of dir ino #15 appears to be a hard
link                                             
JFFS2 error: (297) jffs2_build_inode_pass1: child dir "ftp" (ino #792)
of dir ino #783 appears to be a hard
link                                              
JFFS2 error: (297) jffs2_build_inode_pass1: child dir "log" (ino #793)
of dir ino #784 appears to be a hard
link                                              

This is the on-board flash, of course.  At first I suspected my experiments
with the new 2.6 kernel, but the same problems (in the same places)
occur with the 2.4.26-ts kernel.

I've now spotted a couple of funnies in the filesystem, such as this:
# ls /dev/vc
...[snip]...
crw-------    1 root     root       4,  41 Jan  1 00:00
41                     
crw-------    1 root     root       4,  42 Jan  1 00:00
42                     
-rw-r--r--    1 root     root        31152 Jan  1 00:03
43                     
drwxr-xr-x    3 root     root            0 Jan  1 00:04
44                     
-rw-------    2 root     root       307200 Jan  1 00:04
45                     
crw-------    1 root     root       4,  46 Jan  1 00:00
46                     
crw-------    1 root     root       4,  47 Jan  1 00:00
47                     
crw-------    1 root     root       4,  48 Jan  1 00:00
48                     
...[snip]...

Have I over-used my flash chip?

Is there a way to rejuvenate it?

I typically build an image using mkfs.jffs2, and then "dd" it to
/dev/mtdblock/1.
Naturally, I test with an NFS root until it's as good as I can get it,
before
committing it to flash.  So I can say that I've done this no more than
20 times,
to the board, probably a lot less.  Also, I always mount / as read-only
unless I'm
performing surgery on the filesystem;  all writable files are moved into
/dev/ram.

Would it be better from the point of view of remapping bad blocks,
wear-levelling,
etc., if I were to simply "rm" my old files and "cp" in the new ones,
instead of
replacing the whole contents of flash?

How many cycles should the chip last?

Andrew


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Great things are happening at Yahoo! Groups.  See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/CFFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


<Prev in Thread] Current Thread [Next in Thread>
  • [ts-7000] Puzzling JFFS2 warning, Andrew Gaylard <=
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU