From: Ben Gardiner <bengardiner@nanometrics.ca>
To: "Matthew L. Creech" <mlcreech@gmail.com>
Cc: MTD list <linux-mtd@lists.infradead.org>
Subject: Re: ubifs_decompress: cannot decompress ...
Date: Tue, 31 May 2011 12:10:47 -0400 [thread overview]
Message-ID: <BANLkTim+sNbXG3yk_DGZk4=+0Za+gb65BA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinyQ1hoRDzJ8QKNZYP1m8X+AyPUGQ@mail.gmail.com>
Hi Matthew,
On Tue, May 31, 2011 at 11:47 AM, Matthew L. Creech <mlcreech@gmail.com> wrote:
> On Mon, May 30, 2011 at 8:29 AM, Ben Gardiner
> <bengardiner@nanometrics.ca> wrote:
>>
>> I don't see any debug statements in lzo1x_decompress_safe() that can
>> be enabled, so you might want to add some printing to
>> lzo1x_decompress_safe() or at least print the non-ok return code of
>> lzo1x_decompress_safe() in lzo_decompress() to get an idea of how the
>> decompressor is failing.
>>
>
> Looks like it's returning LZO_E_LOOKBEHIND_OVERRUN. I don't know what
> that indicates, but there is trailing 0xff data in the block to be
> decompressed if that matters:
Interesting -- does the trailing 0xff have ECC set, or is it erased
pages of 0xff?
> XXXX: LZO_E_LOOKBEHIND_OVERRUN
Can't say much more about this than lzo-2.05/doc/LZOAPI.TXT [1] does:
LZO_E_LOOKBEHIND_OVERRUN
Your data is corrupted.
> UBIFS error (pid 428): ubifs_decompress: cannot decompress 1010 bytes,
> compressor lzo, error -22
> 00000000: 00 0f 69 6e 3a 61 74 74 72 00 c2 38 1c 03 39 03 ..in:attr..8..9.
> 00000010: 2f 30 31 2f 6d 57 43 2f 2e 56 61 6c 75 65 4d 61 /01/mWC/.ValueMa
> 00000020: 78 3a 61 91 03 94 31 72 00 69 6e d0 03 00 01 37 x:a...1r.in....7
> 00000030: 1c 03 3d 01 2f 53 65 72 69 61 6c 4e 75 6d 62 65 ..=./SerialNumbe
> 00000040: 72 2f 98 07 98 03 00 0a 04 2f 03 63 01 2f 53 6f r/......./.c./So
> 00000050: 66 74 77 61 72 65 2f 43 6f 6d 6d 61 6e 64 73 2f ftware/Commands/
> 00000060: 6e 65 78 74 d2 01 49 44 29 bc 00 03 06 47 04 81 next..ID)....G..
> 00000070: 0d 03 28 c0 00 00 04 44 61 74 61 20 53 65 72 76 ..(....Data Serv
> 00000080: 65 72 73 2f 42 41 43 6e 65 74 2d 49 50 c4 01 0b ers/BACnet-IP...
> 00000090: 44 65 76 69 63 65 49 6e 73 74 61 6e 63 65 29 14 DeviceInstance).
> 000000a0: 01 05 00 f7 28 41 04 81 03 02 20 0c 1f 01 4d 41 ....(A.... ...MA
> 000000b0: 43 29 08 01 03 02 19 42 04 81 05 20 0d 07 01 4e C).....B... ...N
> 000000c0: 61 6d 2a 14 02 02 02 18 3c 03 7b 20 02 04 01 07 am*.....<.{ ....
> 000000d0: 42 4d 44 41 64 64 72 65 73 73 2a fc 01 02 1d 40 BMDAddress*....@
> 000000e0: 04 81 01 20 05 f4 00 06 54 69 6d 65 54 6f 4c 69 ... ....TimeToLi
> 000000f0: 76 2b f5 01 1e 20 05 f4 01 02 61 73 65 49 64 80 v+... ....aseId.
> 00000100: 36 2a f5 01 20 20 05 f4 03 07 44 65 66 61 75 6c 6*.. ....Defaul
> 00000110: 74 4e 65 74 2f e4 07 03 02 1a 46 04 81 0d 20 01 tNet/.....F... .
> 00000120: 00 03 00 02 45 6e 61 62 6c 65 42 61 73 65 46 6f ....EnableBaseFo
> 00000130: 72 47 61 74 65 77 61 79 2a 24 02 02 1f 45 04 81 rGateway*$...E..
> 00000140: 0b 20 0e 18 01 03 52 6f 75 74 65 64 2a 14 01 02 . ....Routed*...
> 00000150: 21 50 04 81 21 20 01 14 01 c2 07 30 31 3e 84 09 !P..! .....01>..
> 00000160: 03 01 f4 4b 04 81 17 20 17 40 01 2d a8 09 02 24 ...K... .@.-...$
> 00000170: 4c 04 81 19 20 17 2c 01 2e d0 09 01 23 3a 03 77 L... .,.....#:.w
> 00000180: 20 07 2c 01 2d 1d 02 1c 20 05 d0 0c b0 24 33 cc .,.-... ....$3.
> 00000190: 07 02 1b 00 00 00 11 6c 00 00 3f 6a 68 2e 73 ec .......l..?jh.s.
> 000001a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000001b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000001c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000001d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000001e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000001f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000210: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000220: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000230: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000240: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000250: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000260: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000270: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000290: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000002a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000002b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000002c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000002d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000002e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000002f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000310: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000320: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000330: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000340: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000350: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000360: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000370: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 00000390: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000003a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000003b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000003c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000003d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000003e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
> 000003f0: ff ff
> UBIFS error (pid 428): read_block: bad data node (block 388, inode 556196)
> UBIFS error (pid 428): do_readpage: cannot read page 388 of inode
> 556196, error -22
Could it be possible that writing the page was interrupted? I guess
the CRC checks above decompress would catch that though.
Sorry I can't be of more help here.
Best Regards,
Ben Gardiner
[1] http://www.oberhumer.com/opensource/lzo/download/
---
Nanometrics Inc.
http://www.nanometrics.ca
next prev parent reply other threads:[~2011-05-31 16:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 21:12 ubifs_decompress: cannot decompress Matthew L. Creech
2011-05-30 12:29 ` Ben Gardiner
2011-05-31 15:47 ` Matthew L. Creech
2011-05-31 16:10 ` Ben Gardiner [this message]
2011-05-31 21:47 ` Matthew L. Creech
2011-06-01 7:51 ` Artem Bityutskiy
2011-06-02 4:30 ` Matthew L. Creech
2011-06-02 18:59 ` Matthew L. Creech
2011-06-06 9:58 ` Artem Bityutskiy
2011-06-06 16:04 ` Matthew L. Creech
2011-06-06 16:18 ` Artem Bityutskiy
2011-06-06 19:52 ` Matthew L. Creech
2011-06-07 4:34 ` Artem Bityutskiy
2011-06-07 20:41 ` Matthew L. Creech
2011-06-08 14:11 ` Artem Bityutskiy
2011-06-08 17:50 ` Matthew L. Creech
2011-06-09 12:10 ` Artem Bityutskiy
2011-06-20 15:35 ` Matthew L. Creech
2011-06-07 10:24 ` Artem Bityutskiy
2011-06-03 4:32 ` Artem Bityutskiy
2011-06-01 8:02 ` Artem Bityutskiy
2011-06-01 8:07 ` Artem Bityutskiy
2011-06-01 8:39 ` Artem Bityutskiy
2011-06-02 4:34 ` Matthew L. Creech
2011-06-01 7:48 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTim+sNbXG3yk_DGZk4=+0Za+gb65BA@mail.gmail.com' \
--to=bengardiner@nanometrics.ca \
--cc=linux-mtd@lists.infradead.org \
--cc=mlcreech@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).