public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Scott Zhang <macromarship@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs_decompress: cannot decompress 2293 bytes, compressor lzo, error -22
Date: Thu, 14 Apr 2022 19:24:13 +0200	[thread overview]
Message-ID: <20220414192413.0db7ef46@xps13> (raw)
In-Reply-To: <CABy3iKxexzn2TnYVV8k0=_onqdrjQGoPeLMOd2q8cqzVECvBWw@mail.gmail.com>

Hi Scott,

macromarship@gmail.com wrote on Fri, 15 Apr 2022 00:45:23 +0800:

> Hello. Everyone.
>      I encountered a strange problem about ubifs. My embed linux runs
> well normally. But after about 3-4 days, developing php application,
> copying files etc.. the /opt partition when read, the system become
> very slow. After check dmesg
> the output contains full of debug logs as below.
> 
> [17588.040000] UBIFS error (ubi0:0 pid 15691): do_readpage: cannot
> read page 15 of inode 396, error -22
> [17590.080000] UBIFS error (ubi0:0 pid 15695): ubifs_decompress:
> cannot decompress 2293 bytes, compressor lzo, error -22
> [17590.090000] UBIFS error (ubi0:0 pid 15695): do_readpage: bad data
> node (block 15, inode 396)
> lots of hex dump, seems normal data
> 
> Based on my understanding of ubi and ubi fs. The bottomest nand driver
> has the ecc correction, then ubi has crc32 to verify data write and
> read. Then when data come to ubifs, the data should be always correct.
> Anything wrong will be reported firstly by ubi below or mtd nand
> driver below.
> So the msg shows above confuse me. Why did decompress fail for passed
> crc32 data?
> Is there anyway to simple drop the block 15, inode 396 so no warning
> anymore. Even so many logs dumped ,the system continues runs , but
> ramdomly hangs. Maybe no hang, the linux run led continues blink,
> network led blink, the ping ip is not react.
> Because I port the nand driver myself, and port everything to make
> nand working. So Is there a possibility I make ecc checksum wrong,
> then get this wierd problem?
> 
> I googled first, and only see related discuss on 2011 but can't see it help.
> https://linux-mtd.infradead.narkive.com/c65SedYp/ubifs-decompress-cannot-decompress

Hello Scott, if you are unsure about your NAND implementation you can
run all the nand/ubi tests available in the mtd-utils test suite (also
available as a Buildroot package):
https://git.infradead.org/mtd-utils.git

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2022-04-14 17:24 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 [this message]
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
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=20220414192413.0db7ef46@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=macromarship@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