From: Artem Bityutskiy <dedekind1@gmail.com>
To: Guilherme de Oliveira Costa <guilherme.oliveira@autotrac.com.br>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Filesystems over UBI can't handle badblocks
Date: Thu, 25 Feb 2016 12:49:51 +0200 [thread overview]
Message-ID: <1456397391.4719.30.camel@gmail.com> (raw)
In-Reply-To: <7F9DB42F7DDA544EA3EB31D694929A30EB84DA@PERU.autotrac.corp>
On Wed, 2016-02-24 at 20:08 +0000, Guilherme de Oliveira Costa wrote:
> As you can see, UBI starts just fine, and I'm able to initialize
> ubiblk and at least mount the filesystem. I thought UBI was supposed
> to make any badblocks transparent to the upper layers... Is there a
> problem with that tought, or did my manual tampering (with nand
> markbad) got in the way of UBI's bad block management capabilities?
It is right that UBI makes things transparent to upper layers. However,
this is true only if you follow a set of reasonable rules, like you do
not go and change the MTD partition directly, all the changes go via
UBI.
Marking an eraseblock as bad is a change, and it should be done via
UBI, not directly via MTD.
Now, how to do it via UBI? I think this is not supported, but it can be
implemented, I believe.
next prev parent reply other threads:[~2016-02-25 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 20:08 Filesystems over UBI can't handle badblocks Guilherme de Oliveira Costa
2016-02-24 21:30 ` Richard Weinberger
2016-02-25 9:02 ` Ricard Wanderlof
2016-02-25 10:49 ` Artem Bityutskiy [this message]
2016-02-25 21:10 ` Richard Weinberger
2016-02-26 8:24 ` Artem Bityutskiy
[not found] <7F9DB42F7DDA544EA3EB31D694929A30EB9762@PERU.autotrac.corp>
2016-02-29 19:06 ` 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=1456397391.4719.30.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=guilherme.oliveira@autotrac.com.br \
--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.