From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.tal.de ([81.92.1.5]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1JFQNh-0005vB-5v for linux-mtd@lists.infradead.org; Thu, 17 Jan 2008 08:45:58 +0000 Received: from [172.16.0.10] (p50825747.dip.t-dialin.net [80.130.87.71]) by smtp.tal.de (SMTP.TAL.DE) with ESMTP id EF90B100FB1 for ; Thu, 17 Jan 2008 09:42:51 +0100 (CET) Message-ID: <478F1509.2090001@mkc-gmbh.de> Date: Thu, 17 Jan 2008 09:42:49 +0100 From: =?ISO-8859-15?Q?Bernd_B=FCttner?= MIME-Version: 1.0 To: linux-mtd@lists.infradead.org Subject: Cleaning JFFS2 errors Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, after working some time with the JFFS2 filesystem (on a uclinux-system with a non-mmu freescale processor) I'm getting errors on every mount like this: jffs2_scan_inode(): CRC failed on node at 0x00c999f0: Read 0xffffffff, calculated 0x7621c0c4 Empty flash at 0x00c99a3c ends at 0x00c99c00 Empty flash at 0x0134201c ends at 0x01342200 jffs2_scan_eraseblock(): Node at 0x01d88df8 {0x1985, 0xe001, 0x0000002f) has invalid CRC 0x1985e001 (calculated 0x392fe03e) JFFS2 notice: (13) read_dnode: node CRC failed on dnode at 0x1341fd4: read 0xffffffff, calculated 0xce9c70e9 The kernel is 2.6.19 from the latest uclinux distribution 20070130. I think these errors are the result of power-loss, misbehaving new drivers and system crashes, and I suppose they are not critical and will be corrected by jffs2 after some time. But delivering such systems to customers doesn't look good. Is there a possibility to force jffs2 to correct these errors at once? I hope so. Bernd