From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dongsheng Yang <dongsheng.yang@easystack.cn>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: starvik@axis.com, jesper.nilsson@axis.com,
Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
shengyong1@huawei.com, linux-cris-kernel@axis.com,
Brian Norris <computersforpeace@gmail.com>,
Richard Weinberger <richard@nod.at>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
dooooongsheng.yang@gmail.com, jschultz@xes-inc.com,
fabf@skynet.be, mtownsend1973@gmail.com,
linux-mtd@lists.infradead.org,
Colin King <colin.king@canonical.com>,
asierra@xes-inc.com, dmitry.torokhov@gmail.com,
Dongsheng Yang <dongsheng081251@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: MTD RAID
Date: Mon, 22 Aug 2016 10:27:21 +0300 [thread overview]
Message-ID: <1471850841.15722.13.camel@gmail.com> (raw)
In-Reply-To: <57BA6FFA.6000601@easystack.cn>
On Mon, 2016-08-22 at 11:22 +0800, Dongsheng Yang wrote:
> As I explained above, MTD RAID is not just a solution for reliability
> problem for MLC/TLC.
Could you please answer these questions.
1. Does MTD raid work on MLC or is it SLC-only?
2. If I am building RAID-0, I have 2 flash chips, one has every even
block bad, the other has every odd block bad. What happens?
3. Same question, but for RAID-1.
4. Suppose I have RAID-1 like in this picture:
https://en.wikipedia.org/wiki/Standard_RAID_levels#/media/File:RAID_1.svg
Just assume we have flash chips, not disks, and eraseblocks, not
sectors.
Suppose eraseblock A1 goes bad. What happens next?
5. Suppose I have RAID-0 like here:
https://en.wikipedia.org/wiki/Standard_RAID_levels#/media/File:RAID_0.svg
Again, we are talking about chips and eraseblocks here.
What happens if A1 goes bad.
Thanks!
next prev parent reply other threads:[~2016-08-22 7:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+qeAOpuZ0CXZP8tCWdhoVvTEKAw26gtz63-UJmQ4XLSXAd=Yg@mail.gmail.com>
2016-08-19 6:49 ` MTD RAID Boris Brezillon
2016-08-19 7:08 ` Dongsheng Yang
2016-08-19 7:15 ` Dongsheng Yang
2016-08-19 7:28 ` Dongsheng Yang
2016-08-19 8:20 ` Boris Brezillon
[not found] ` <CA+qeAOrSAi9uTHGCi-5cAJpM_O45oJUihNP-rHHa1FWL7_ZKHQ@mail.gmail.com>
2016-08-19 9:37 ` Boris Brezillon
2016-08-19 10:22 ` Dongsheng Yang
2016-08-19 11:36 ` Boris Brezillon
[not found] ` <57B6CC7B.1060208@easystack.cn>
2016-08-19 9:47 ` Richard Weinberger
2016-08-19 10:30 ` Dongsheng Yang
2016-08-19 10:30 ` Artem Bityutskiy
2016-08-19 10:38 ` Dongsheng Yang
[not found] ` <AL*AZwAyAecQSM1UjjjNxao0.3.1471605640762.Hmail.dongsheng.yang@easystack.cn>
2016-08-19 11:55 ` Boris Brezillon
2016-08-22 4:01 ` Dongsheng Yang
2016-08-22 7:09 ` Boris Brezillon
[not found] ` <57BA6FFA.6000601@easystack.cn>
2016-08-22 7:07 ` Boris Brezillon
2016-08-22 7:27 ` Artem Bityutskiy [this message]
[not found] ` <CAAp9bSh-geStbHpA6+vYdLfNLcinWkfVLOGmX4kdRbja+d2MdA@mail.gmail.com>
2016-08-22 14:54 ` Artem Bityutskiy
2016-08-22 15:30 ` David Woodhouse
2016-08-23 3:44 ` Dongsheng Yang
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=1471850841.15722.13.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=asierra@xes-inc.com \
--cc=boris.brezillon@free-electrons.com \
--cc=colin.king@canonical.com \
--cc=computersforpeace@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dongsheng.yang@easystack.cn \
--cc=dongsheng081251@gmail.com \
--cc=dooooongsheng.yang@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fabf@skynet.be \
--cc=jesper.nilsson@axis.com \
--cc=jschultz@xes-inc.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mtownsend1973@gmail.com \
--cc=richard@nod.at \
--cc=shengyong1@huawei.com \
--cc=starvik@axis.com \
--cc=yangds.fnst@cn.fujitsu.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 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.