CRC errors when continuous fseek/fputs on JFFS2
Jörn Engel
joern at wohnheim.fh-wedel.de
Tue May 16 11:31:31 EDT 2006
On Tue, 16 May 2006 08:01:54 -0700, syed khader wrote:
>
> jffs2_read_inode_range: offset 139961, end 143360
> Reading 139961-139964 from node at 0x0017c9e4 (3)
> Node read from 0017c9e4: node_crc 57239698, calculated
> CRC 57239698. dsize 4, csize 4, offset 222b9, buf
> 00c972b9
> Read 4 bytes to 00c09b60
> Data CRC 675ef222 != calculated CRC 83b8ee96 for node
> at 0017c9e4
> node read done
This is the only mismatch I could find in your log. What I couldn't
find was the matching write to 0x0017c9e4. Still unable to see the
actual bug. Hmm.
Can you start out with a fresh image, run your testcase and get a
complete log? I hope that it contains both a crc mismatch like this
and the write of the node before.
Quite likely the log will be too large for this list. A link to a
webpage would be sufficient, if that is possible.
Jörn
--
I don't understand it. Nobody does.
-- Richard P. Feynman
More information about the linux-mtd
mailing list