From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ernst.netinsight.se ([194.16.221.21]) by bombadil.infradead.org with smtp (Exim 4.69 #1 (Red Hat Linux)) id 1MfX4J-0001Kd-TV for linux-mtd@lists.infradead.org; Mon, 24 Aug 2009 10:46:36 +0000 Message-ID: <4A926F79.4030700@users.sourceforge.net> Date: Mon, 24 Aug 2009 12:46:17 +0200 From: =?ISO-8859-1?Q?Anders_Grafstr=F6m?= MIME-Version: 1.0 To: linux newbie Subject: Re: JFFS2 crash in linux-2.6.30 References: <1c3f4270908211108w416019deh9aa4b2575d6a1b82@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Manoj , linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , linux newbie wrote: > I tried this patch, after which I am not getting crash, but instead it shows > cp: input/output error. and this is not consistent. somtimes, file > copying is perfect and some times its not. You get this when you write to a dnode whose previous data resides in a NAND block that has gone bad. Have you set CONFIG_JFFS2_FS_WBUF_VERIFY?