All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Morand, Guy" <Guy.Morand@comet.ch>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS corruption and UBI + unstable bit questions
Date: Fri, 27 Mar 2015 16:50:19 +0100	[thread overview]
Message-ID: <55157C3B.20500@nod.at> (raw)
In-Reply-To: <68AC191B3EB2874F99C36CD9CA3A6D42196181@cgpmbx01.comet.ch>

Am 27.03.2015 um 14:30 schrieb Morand, Guy:
> Hi,
> 
> Thanks for clarifying!
> 
>> But it depends on the type of the corruption.
> What do you mean by "type of the corruption". Is it about a PEB containing the 
> volume table corrupting every volumes on the MTD device? I can't imagine a PEB
> containing "regular data" corrupting the whole MTD device or correct me if I'm 
> wrong! I guess this should be extremely rare as we don't update the volume table 
> every day ...

We save the volume table twice. But you can't expect that UBI or UBIFS will
survive perfectly fine if random PEBs tun out of the sudden bad.

>> Okay. That's what I thought. I've never seen the issue on serious hardware.
> Serious hardware, does that mean with seriously select components?

Yes.

Thanks,
//richard

      reply	other threads:[~2015-03-27 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:00 UBIFS corruption and UBI + unstable bit questions Morand, Guy
2015-03-26 16:45 ` Richard Weinberger
2015-03-26 17:21   ` AW: " Morand, Guy
     [not found]   ` <68AC191B3EB2874F99C36CD9CA3A6D42195ED8@cgpmbx01.comet.ch>
2015-03-26 18:17     ` Richard Weinberger
2015-03-27 13:30       ` Morand, Guy
2015-03-27 15:50         ` 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=55157C3B.20500@nod.at \
    --to=richard@nod.at \
    --cc=Guy.Morand@comet.ch \
    --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 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.