From: Barak Adam <BAdam@adva.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: RE: UBIFS corruption in empty space during mount
Date: Mon, 2 Nov 2020 06:06:25 +0000 [thread overview]
Message-ID: <75f2f7306c284860beb1769b93d54269@adva.com> (raw)
In-Reply-To: <1907654217.241602.1604006369174.JavaMail.zimbra@nod.at>
Hi Richard,
It is detected as an empty area by UBIFS. Regarding bitflips, I am not sure. I am running it with debug printouts, to dump the corruption and analyze it.
Any other idea how to detect if the underlying corruption is bitflips or something else?
The returned error by the lower layer is -EBADMSG which I guess indicates an unrecoverable ECC error in the media.
Thanks,
Barak
-----Original Message-----
From: Richard Weinberger <richard@nod.at>
Sent: Thursday, October 29, 2020 11:19 PM
To: Barak Adam <BAdam@adva.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS corruption in empty space during mount
External email: [richard@nod.at]
......................................................................
Barak,
----- Ursprüngliche Mail -----
>> Von: "Barak Adam" <BAdam@adva.com>
>> Thanks Richard.
>>
>> I already applied those patches, but the issue is not yet covered / resolved.
>>
>> What kind of a fix should I apply to the driver layer - raise ECC
>> errors for the upper layers even when ready empty / erased area ?
>Maybe you're facing something else. Did you verify that it is really flipped bits in empty space?
>Thanks,
>//richard
Please see our privacy statement at https://www.adva.com/en/about-us/legal/privacy-statement for details of how ADVA processes personal information.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-11-02 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 4:48 UBIFS corruption in empty space during mount Barak Adam
2020-10-29 10:36 ` Richard Weinberger
2020-10-29 14:52 ` Barak Adam
2020-10-29 21:19 ` Richard Weinberger
2020-11-02 6:06 ` Barak Adam [this message]
2020-11-02 7:44 ` 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=75f2f7306c284860beb1769b93d54269@adva.com \
--to=badam@adva.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).