From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wohnheim.fh-wedel.de ([213.39.233.138]) by canuck.infradead.org with esmtp (Exim 4.62 #1 (Red Hat Linux)) id 1Fg1WP-0008Kp-Fa for linux-mtd@lists.infradead.org; Tue, 16 May 2006 11:31:54 -0400 Date: Tue, 16 May 2006 17:31:31 +0200 From: =?iso-8859-1?Q?J=F6rn?= Engel To: syed khader Message-ID: <20060516153131.GD11656@wohnheim.fh-wedel.de> References: <20060516142618.GB11656@wohnheim.fh-wedel.de> <20060516150154.89887.qmail@web37901.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060516150154.89887.qmail@web37901.mail.mud.yahoo.com> Cc: linux-mtd@lists.infradead.org Subject: Re: CRC errors when continuous fseek/fputs on JFFS2 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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