Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Barak Adam <BAdam@adva.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS corruption in empty space during mount
Date: Mon, 2 Nov 2020 08:44:31 +0100 (CET)	[thread overview]
Message-ID: <809847959.256251.1604303071010.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <75f2f7306c284860beb1769b93d54269@adva.com>

Barak,

----- Ursprüngliche Mail -----
> Von: "Barak Adam" <BAdam@adva.com>
> An: "richard" <richard@nod.at>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> Gesendet: Montag, 2. November 2020 07:06:25
> Betreff: RE: UBIFS corruption in empty space during mount

> 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?

I think it is the over way around. UBIFS expects empty space but finds something else.
Find the message in UBIFS and dump the buffer to dmesg. :-)

Thanks,
//richard

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

      reply	other threads:[~2020-11-02  7:45 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
2020-11-02  7:44         ` 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=809847959.256251.1604303071010.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=BAdam@adva.com \
    --cc=linux-mtd@lists.infradead.org \
    /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