From: Richard Weinberger <richard@nod.at>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Scott Zhang <macromarship@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Richard Weinberger <richard.weinberger@gmail.com>
Subject: Re: ubifs_decompress: cannot decompress 2293 bytes, compressor lzo, error -22
Date: Tue, 19 Apr 2022 09:44:30 +0200 (CEST) [thread overview]
Message-ID: <542373121.266606.1650354270993.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20220419093317.7fe2ae6c@xps13>
----- Ursprüngliche Mail -----
> Did you run the various nand tests besides nandbiterrs? If they all
> pass then maybe Richard will be more helpful than I am...
[...]
>>
>> But I noticed the lzo decompress error is still there.
>> I did following actions to test.
>> /dev/mtd3 is mounted on /opt using ubifs.
>> tar zcvf /root/opt.tar.gz /opt (done without error)
>> format /opt.
>> tar zxvf /root/opt.tar.gz -C /
How did you create ubifs?
Does your nand driver pass ubi tests?
>> Then when I run php program which is in opt. I saw dmesg
>> [ 118.850000] UBIFS error (ubi0:0 pid 1526): ubifs_decompress: cannot
>> decompress 2293 bytes, compressor lzo, error -22
>> [ 118.860000] UBIFS error (ubi0:0 pid 1526): do_readpage: bad data
>> node (block 15, inode 396)
>> [ 118.870000] UBIFS error (ubi0:0 pid 1526): do_readpage: cannot read
>> page 15 of inode 396, error -22
>> [ 118.880000] UBIFS error (ubi0:0 pid 1526): ubifs_decompress: cannot
>> decompress 2293 bytes, compressor lzo, error -22
>> [ 118.900000] UBIFS error (ubi0:0 pid 1526): do_readpage: bad data
>> node (block 15, inode 396)
>> [ 118.900000] UBIFS error (ubi0:0 pid 1526): do_readpage: cannot read
>> page 15 of inode 396, error -22
>> [ 118.920000] UBIFS error (ubi0:0 pid 1526): ubifs_decompress: cannot
>> decompress 2293 bytes, compressor lzo, error -22
>> [ 118.930000] UBIFS error (ubi0:0 pid 1526): do_readpage: bad data
>> node (block 15, inode 396)
>> [ 118.940000] UBIFS error (ubi0:0 pid 1526): do_readpage: cannot read
>> page 15 of inode 396, error -22
>>
>> I removed the ubifs_dump_node call to avoid many dump text. The
>> problem is when I run php program, lots of above logs dumped.
>> But I don't see any effect of the above logs. the program seems running.
>> Is there a possibility the underlying nand driver data is ok, but the
>> lzo compress/decompress code has bugs ? I am running linux-5.4.y
>> cloned from kernel.org.
Does the problem only happen with lzo?
Please re-test with no compressor enabled (compr=none) and also mount with
the chk_data_crc mount option.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-19 7:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 16:45 ubifs_decompress: cannot decompress 2293 bytes, compressor lzo, error -22 Scott Zhang
2022-04-14 17:24 ` Miquel Raynal
2022-04-15 4:38 ` Scott Zhang
2022-04-15 8:29 ` Miquel Raynal
2022-04-19 2:05 ` Scott Zhang
2022-04-19 7:33 ` Miquel Raynal
2022-04-19 7:44 ` Richard Weinberger [this message]
2022-04-19 9:03 ` Scott Zhang
2022-04-19 9:11 ` Scott Zhang
2022-04-20 3:00 ` Scott Zhang
2022-04-20 6:26 ` Richard Weinberger
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=542373121.266606.1650354270993.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=macromarship@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard.weinberger@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