From: Richard Weinberger <richard.weinberger@gmail.com>
To: Mickael Chazaux <mickael.chazaux@etictelecom.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs_check_node: bad CRC
Date: Tue, 13 Aug 2019 23:41:50 +0200 [thread overview]
Message-ID: <CAFLxGvzF8iDJG_rTqGwrLdmFsehaLxD4os50_QLZTMjytVQ9Dw@mail.gmail.com> (raw)
In-Reply-To: <5D3FF1A6.7050407@etictelecom.com>
On Tue, Jul 30, 2019 at 9:28 AM Mickael Chazaux
<mickael.chazaux@etictelecom.com> wrote:
> > That easy?
> > Hmm, sounds a bit like a bug in your NAND driver. Did you test it?
> >
>
> Sorry, I meant : the "nand-image.img" file is coming from a corrupted device.
> I ran the mtd_* kernel module tests yesterday. All seems good, but the torture test
> is not yet finished (see below).
Ahh, now it makes more sense.
> The problem occured in the field on several devices, and I cannot reproduce it
> in the lab.
It sounds a bit like a memory corruption.
> > Please also disable compression in UBIFS, then the read back data maybe gives
> > you a hint what went wrong.
>
> In the corrupted node I see data from syslog. This system is a bit different
> than the others we usually make, as there are more power cuts and more log writes.
Hmm. Power cuts or many writes should not trigger such a corruption.
I'd expect ECC errors or data structure errors in UBIFS. But not a good ECC
with bad UBIFS data CRC.
But with only one sample it is almost impossible to figure...
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-13 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 13:28 ubifs_check_node: bad CRC Mickael Chazaux
2019-07-29 18:16 ` Richard Weinberger
2019-07-30 7:28 ` Mickael Chazaux
2019-08-13 21:41 ` Richard Weinberger [this message]
2019-08-23 9:24 ` Mickael Chazaux
2019-08-25 19:02 ` 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=CAFLxGvzF8iDJG_rTqGwrLdmFsehaLxD4os50_QLZTMjytVQ9Dw@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mickael.chazaux@etictelecom.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).