From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: syed khader <sk.syed@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CRC errors when continuous fseek/fputs on JFFS2
Date: Tue, 16 May 2006 17:31:31 +0200 [thread overview]
Message-ID: <20060516153131.GD11656@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20060516150154.89887.qmail@web37901.mail.mud.yahoo.com>
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
next prev parent reply other threads:[~2006-05-16 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060516061354.GA18958@wohnheim.fh-wedel.de>
2006-05-16 12:40 ` CRC errors when continuous fseek/fputs on JFFS2 syed khader
2006-05-16 14:26 ` Jörn Engel
2006-05-16 15:01 ` syed khader
2006-05-16 15:31 ` Jörn Engel [this message]
2006-05-17 5:12 ` syed khader
2006-05-17 6:25 ` zlib compression is failing syed khader
2006-05-17 9:10 ` Jörn Engel
2006-05-17 10:42 ` Josh Boyer
2006-05-17 11:22 ` syed khader
2006-05-17 13:19 ` Jörn Engel
2006-05-17 13:48 ` syed khader
2006-05-17 14:28 ` David Woodhouse
2006-05-15 15:15 CRC errors when continuous fseek/fputs on JFFS2 syed khader
2006-05-15 15:46 ` Jörn Engel
2006-05-15 15:57 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060516153131.GD11656@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=sk.syed@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox