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: Sun, 25 Aug 2019 21:02:14 +0200 [thread overview]
Message-ID: <CAFLxGvyLqd2yFRQLQau82MV2ud0AUxsdeXVa5fU7j=ZsJ52YEg@mail.gmail.com> (raw)
In-Reply-To: <5D5FB0CC.3050502@etictelecom.com>
On Fri, Aug 23, 2019 at 11:25 AM Mickael Chazaux
<mickael.chazaux@etictelecom.com> wrote:
> > 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...
> >
>
> Memory corruption as in some kind of buffer overflow or use after free ? or physical
> bus errors? Anyway I think I will implement some mitigations at the application level,
> (eg. less log messages, recovery by creating a new volume, copy the now-readonly data,
> rename the volume) because the haystack just got too big for the needle.
This could be caused my any kind of corruption. Do you monitor your devices?
Maybe the crash also once in a while and you notice only the case when bad data
is written to flash.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-08-25 19:02 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
2019-08-23 9:24 ` Mickael Chazaux
2019-08-25 19:02 ` Richard Weinberger [this message]
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='CAFLxGvyLqd2yFRQLQau82MV2ud0AUxsdeXVa5fU7j=ZsJ52YEg@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).