From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vw0-f49.google.com ([209.85.212.49]) by canuck.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1QTcIG-0000Cw-I6 for linux-mtd@lists.infradead.org; Mon, 06 Jun 2011 16:04:45 +0000 Received: by vws8 with SMTP id 8so3831434vws.36 for ; Mon, 06 Jun 2011 09:04:42 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1307354316.3112.19.camel@localhost> References: <1306914686.4405.53.camel@localhost> <1307354316.3112.19.camel@localhost> Date: Mon, 6 Jun 2011 12:04:42 -0400 Message-ID: Subject: Re: ubifs_decompress: cannot decompress ... From: "Matthew L. Creech" To: dedekind1@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: Ben Gardiner , MTD list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Jun 6, 2011 at 5:58 AM, Artem Bityutskiy wrote: > > So the corruption starts exactly at the NAND page boundary. This makes > me believe that the reason is most probably power cut recovery. But you > say your client ensures there were none... > > Yes, you are right that info from past is gone... What I'd like to see > is a dump of the whole LEB. Could you please add 'dbg_dump_leb()' - > basically I want to look if this LEB was passed through GC. > [Repost, gmail mangled my node dump] The dbg_dump_leb() call fails due to a bad CRC; I've posted its output plus the corresponding raw LEB dump (obtained via mtd->read_oob()) here: http://mcreech.com/work/ubifs-decompress-err-rawleb.txt -- Matthew L. Creech