jffs2 tests

[Xavier DEBREUIL <xde@inventel.fr>]

Hello,
I do a similar test on jffs2 (20010802) as Frederic Giasson did :
1- copy randomly generated files of different sizes several times to
fill the jffs2 partition
2- df
3- remove all files
4- df

at step 4, most of the time I have :
/dev/mtdblock2            3200       648      2552  20%
/mnt/jffs2/jffs2_0
and from time to time :
/dev/mtdblock2            3200       904      2296  28%
/mnt/jffs2/jffs2_0
Nevertheless, as the following copy is able to copy the same amount of
files, it should be due to the latency of the garbage collector work
(confirm).

The only thing that seems odd to me is the occurence from time to time
of the following :

 rm -R /mnt/jffs2/jffs2_0/*
Unknown INCOMPAT nodetype C002 at 001B1588
jffs2_read_inode(): No data nodes found for ino #23289
Eep. read_inode() failed for ino #23289
Unknown INCOMPAT nodetype C002 at 000E1A8C
jffs2_read_inode(): No data nodes found for ino #23290
Eep. read_inode() failed for ino #23290

the unknown nodetype is always C002

What kind of debug is worth to be printed out to get more information
about that problem ?

Xavier