From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ey0-f177.google.com ([209.85.215.177]) by canuck.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1QRgHS-0001PE-9h for linux-mtd@lists.infradead.org; Wed, 01 Jun 2011 07:55:54 +0000 Received: by eyh6 with SMTP id 6so2156004eyh.36 for ; Wed, 01 Jun 2011 00:55:51 -0700 (PDT) Subject: Re: ubifs_decompress: cannot decompress ... From: Artem Bityutskiy To: "Matthew L. Creech" In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Wed, 01 Jun 2011 10:51:26 +0300 Message-ID: <1306914686.4405.53.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 Tue, 2011-05-31 at 17:47 -0400, Matthew L. Creech wrote: > Unfortunately it's not repeatable enough for us to capture adequate > debug output - we've had several devices logging extensive debug > output via netconsole for months now, but none have recreated this > problem so far under those conditions. How this happens? What do you do? Does this happen after mount when you first read your data? Or this happens at some point while you stress testing your system? Or this happens after a power cut? -- Best Regards, Artem Bityutskiy (Артём Битюцкий)