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 1QRzcR-0008AB-S4 for linux-mtd@lists.infradead.org; Thu, 02 Jun 2011 04:34:52 +0000 Received: by vws8 with SMTP id 8so509176vws.36 for ; Wed, 01 Jun 2011 21:34:50 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1306915328.4405.62.camel@localhost> References: <1306915328.4405.62.camel@localhost> Date: Thu, 2 Jun 2011 00:34:50 -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 Wed, Jun 1, 2011 at 4:02 AM, Artem Bityutskiy wrote: > > 4. The fixup feature might have broke this - we might for some reason > read less data than there. Although I see FFs start at offset 416, which > is strange. > Also, I can rule this possibility out - although the device is now running a recent kernel with the fix-up code present, it was upgraded last week from an older version. So the UBIFS image it was originally programmed with (and is still using) didn't have the fixup flag set. -- Matthew L. Creech