From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lazybastard.de ([212.112.238.170] helo=longford.logfs.org) by bombadil.infradead.org with esmtps (Exim 4.68 #1 (Red Hat Linux)) id 1K8XQo-0005h9-BY for linux-mtd@lists.infradead.org; Tue, 17 Jun 2008 09:24:51 +0000 Date: Tue, 17 Jun 2008 11:24:34 +0200 From: =?utf-8?B?SsO2cm4=?= Engel To: Matthieu CASTET Subject: Re: [BUG] JFFS2 power loss recovery issues on NAND Message-ID: <20080617092434.GA27539@logfs.org> References: <48570D5A.1050906@call-direct.com.au> <48577212.9070004@parrot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <48577212.9070004@parrot.com> Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org, Alexey Korolev , Iwo Mergler List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 17 June 2008 10:13:06 +0200, Matthieu CASTET wrote: > Iwo Mergler wrote: > > > > About how to fix it - what about making the reading without ECC the default > > and only re-reading with ECC if JFFS2 finds an invalid checksum? > > > But what happen if a but flip happen ? The exact same problem. Changing the default is bogus. Re-reading without ecc on invalid checksums may be the only solution for jffs2, though. Either that or close your eyes and claim that holes in files can happen on power loss. Jörn -- Fancy algorithms are buggier than simple ones, and they're much harder to implement. Use simple algorithms as well as simple data structures. -- Rob Pike