From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [2001:838:3de:1000::2] (helo=fserver.unsec.nl) by canuck.infradead.org with esmtps (Exim 4.43 #1 (Red Hat Linux)) id 1Cw013-0006ak-5P for linux-mtd@lists.infradead.org; Tue, 01 Feb 2005 10:32:34 -0500 From: "Rudi Engelbertink" To: linux-mtd@lists.infradead.org Date: Tue, 1 Feb 2005 16:32:23 +0100 Message-Id: <20050201150810.M93647@unsec.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: jffs2_get_inode_nodes() very very slow List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello, On a 64 MiB NAND Flash I created a jffs2 file system. After several tests especially power fail tests resulting in a lot off CRC and Data CRC errors. This appears not to be a problem except it takes a very long time to check the file system. The initial check (scanning for erased blocks) is done in aproximatly 10 seconds, but after that the jffs2_get_inode_nodes check is running. This process takes up to 8 minutes. During this time the file-system is inaccessible which in oure case a watchdog decides to reboot the system, making it even worse. It appears that the check is done with a stepsize of 16 bytes. On an 64MiB NAND flash it does this check +/- 4 million times. Is there a way to reduce the time to check the file-system and/or how can I recover from these errors. Kind Regards, Rudi. -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. Benjamin Franklin (1706-1790), Letter to Josiah Quincy, Sept. 11, 1773. GnuPG Key fingerprint = 706C E2AC 7AE2 BCEE 04EB A962 0A75 7F9B 07A1 83E8