From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-fx0-f49.google.com ([209.85.161.49]) by canuck.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1QTcZT-0000V1-0a for linux-mtd@lists.infradead.org; Mon, 06 Jun 2011 16:22:31 +0000 Received: by fxm14 with SMTP id 14so3720484fxm.36 for ; Mon, 06 Jun 2011 09:22:28 -0700 (PDT) Subject: Re: ubifs_decompress: cannot decompress ... From: Artem Bityutskiy To: "Matthew L. Creech" In-Reply-To: References: <1306914686.4405.53.camel@localhost> <1307354316.3112.19.camel@localhost> Content-Type: text/plain; charset="UTF-8" Date: Mon, 06 Jun 2011 19:18:11 +0300 Message-ID: <1307377091.3112.100.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: Ben Gardiner , MTD list Reply-To: dedekind1@gmail.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2011-06-06 at 12:04 -0400, Matthew L. Creech wrote: > 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: I have to go home now - could you please improve dbg_dump_leb(). Currently it calls ubifs_scan(), which scans, finds corrupted node, prints corruption information and returns -EUCLEAN and destroys the scanned data. Instead, we could do: 1. Add another parameter to ubifs_scan() which makes it to _not_ free scanned data on corruption. 2. In dbg_dump_leb() when you get -EUCLEAN - just go ahead and print the scanned information instead of exiting. Should not be too difficult to do. -- Best Regards, Artem Bityutskiy (Артём Битюцкий)