ubifs_decompress: cannot decompress ...
dedekind1 at gmail.com
Fri Jun 3 00:32:20 EDT 2011
On Thu, 2011-06-02 at 00:30 -0400, Matthew L. Creech wrote:
> On Wed, Jun 1, 2011 at 3:51 AM, Artem Bityutskiy <dedekind1 at gmail.com> wrote:
> > 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?
> So far there's no discernable pattern. Most of the failed units are
> returns from the field, so we don't know what kind of conditions
> they've been placed in. Some are from our test department, but we
> haven't found anything that might "trigger" the problem in any way.
> The device works fine for some period of time (usually weeks /
> months), then we get complaints about various problems. The reported
> symptoms eventually come down to one of these UBIFS errors. Depending
> on the region which happens to go bad, it can result in breakage of a
> minor feature (because a file we try to read/write after mount
> triggers the error), all the way up to a completely non-functional
> device. I'm not sure if we've ever seen it fail to mount altogether
> (I'll check into that), but we've had several cases in which U-Boot
> couldn't read the kernel image from UBIFS, so the device wouldn't boot
> Linux at all.
> Power cuts are probably not common, though. We have to expect them in
> the product of course, but practically speaking, our service guy
> assures me that a couple of the bad units he shipped me had stable
> power and were rarely/never rebooted. But I can't rule it out with
> Aside from that, it's just normal operation. If the usage pattern
> matters, the only files ever written to in the persistent (UBIFS)
> filesystem are SQLite databases. It's generally light usage, logging
> a variety of measurements once every 5 minutes. I've tried
> stress-testing by running non-stop SQLite operations, recreating the
> normal usage pattern but with a _much_ higher frequency of writes than
> normal. It didn't seem to help reproduce the error - we've yet to
> succeed in making this problem happen under controlled conditions.
> As for this specific error (ubifs_decompress): tomorrow I'll try to
> gather & post additional log data for this device. Thanks!
OK, then this is not about power cuts and unstable bits. First thing
coming to my mind is that your kernel may have some non-UBIFS bugs which
end up in memory corruptions, so UBIFS writes corrupted data to the
But the hexdump you sent shows that you have some non-0xFFs and then
many 0xFFs. Are those trailing 0xFFs part of the node data or not? If
yes, then it does not look like memory corruption, but more like some
BTW, have you run mtd tests? Would you mind to set up torture test on
one of your boards and let it run fore several weeks. I remember we
found a rare DMA bug in our board by running the torture test for long
time. Also, it might be interesting how your HW and SW behave when you
continuously wear out few eraseblocks.
Artem Bityutskiy (Артём Битюцкий)
More information about the linux-mtd