linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Williams <nathan.williams@flightdata.com.au>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBI on dual NAND chips
Date: Fri, 25 Sep 2015 00:22:55 +1000	[thread overview]
Message-ID: <1443104575.7429.49.camel@linux> (raw)
In-Reply-To: <CAFLxGvxN-6EQtzO4z7AsJX1QrGU2Nuf9mhqFqrxyE+dGXDWYqw@mail.gmail.com>

On Thu, 2015-09-24 at 11:02 +0200, Richard Weinberger wrote:
> Using UBI on MLC is not supported yet.
> IOW, you have been warned. ;-)

Thanks. I wasn't sure, despite my background reading.

> > From what I've read, it's possible to use UBI on a concatenated MTD.
> > If I have two identical chips, will these be concatenated automatically?
> 
> You mean using the mtd_concat driver?

Yes.

> > Is creating a single UBI volume over the two NAND chips (and using UBIFS
> > on it) the best way to make use of a redundant NAND chip? Would
> > mirroring data on a second UBI volume offer additional improvements to
> > data reliability?
> 
> Depends on how you define "data reliability".
> You're looking for something like an MTD RAID1 to deal with a dead chip?

Yes that would be ideal. The NAND flash will be used for data logging.
We'd like to use multiple chips to improve our chances of recovering
recorded data in the event that either a chip dies or there are too many
errors.

> > Also, what's the current status of the "unstable bits issue"?
> 
> It is a known issue but nobody cared hard enough so far.
> Mostly due to the fact that nobody actually can trigger it.
> 
> Can you trigger it? If so, I'd like to get access to that hardware
> and have a look.

No I haven't seen it. Our hardware is still in the planning phase.

  reply	other threads:[~2015-09-24 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  2:44 UBI on dual NAND chips Nathan Williams
2015-09-24  9:02 ` Richard Weinberger
2015-09-24 14:22   ` Nathan Williams [this message]
     [not found] <A765B125120D1346A63912DDE6D8B6310BF4CAC4@NTXXIAMBX02.xacn.micron.com>
2015-09-25  4:43 ` Nathan Williams
2015-09-25  5:35   ` Bean Huo 霍斌斌 (beanhuo)

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=1443104575.7429.49.camel@linux \
    --to=nathan.williams@flightdata.com.au \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    /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).