All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Steve deRosier <derosier@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: "corrupt empty space" error on boot?!?
Date: Tue, 03 Mar 2015 09:31:52 +0200	[thread overview]
Message-ID: <1425367912.26652.47.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CALupW3CugdN+cwMZzePAhZSHbGhd9gfjk==DH=7Ezu54Y1BXUA@mail.gmail.com>

On Mon, 2015-03-02 at 08:39 -0800, Steve deRosier wrote:
> Logically, it seems to me that a non ecc protected bit-flip in an
> empty page should be a non-issue. UBI should be able to move the
> block, erase the block, torture/return-to-service and move on with
> it's life.  No data is destroyed or even affected.

Yes, you are right, if there is a corruption, UBIFS can:

1. Try to understand if this is a corruption in empty space or not.
2. If yes, recover the LEB.

But this is not implemented. People keep hitting this issue, but no one
contributed fixes yet.

> A unit not mounting the rootfs because of a bit-flip in _empty_space_
> is unacceptable to us, so I've got to figure out a way to deal with
> this rare event.

Well, improving UBIFS would be one of the possible solutions.

Artem.

  reply	other threads:[~2015-03-03  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 16:39 "corrupt empty space" error on boot?!? Steve deRosier
2015-03-03  7:31 ` Artem Bityutskiy [this message]
2015-03-03 15:25   ` Steve deRosier
2015-03-04  3:31     ` hujianyang

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=1425367912.26652.47.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=derosier@gmail.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 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.