From: Mickael Chazaux <mickael.chazaux@etictelecom.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs_check_node: bad CRC
Date: Fri, 23 Aug 2019 11:24:28 +0200 [thread overview]
Message-ID: <5D5FB0CC.3050502@etictelecom.com> (raw)
In-Reply-To: <CAFLxGvzF8iDJG_rTqGwrLdmFsehaLxD4os50_QLZTMjytVQ9Dw@mail.gmail.com>
On 13/08/2019 23:41, Richard Weinberger wrote:
>
>> 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...
>
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.
Thank you for your help,
Mickael
--
Mickael Chazaux
Software Engineer
Tel : (33) 476 042 006
Fax : (33) 476 042 001
ETIC TELECOM
13, Chemin du Vieux Chêne
38240 MEYLAN
Tel: 33 4 76 04 20 00
fax : 33 4 76 04 20 01
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-23 9:25 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 [this message]
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=5D5FB0CC.3050502@etictelecom.com \
--to=mickael.chazaux@etictelecom.com \
--cc=linux-mtd@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.