From: NeilBrown <neilb@suse.de>
To: Dong Wu <archer.wudong@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: when md raid1 superblock is bad block, what happens
Date: Tue, 6 Aug 2013 11:47:07 +1000 [thread overview]
Message-ID: <20130806114707.0c3ffc07@notabene.brown> (raw)
In-Reply-To: <CAAL-TMcqej1YYYoCJr3XV7GONYzUR4=8poMnzMcrzTjP7N84KQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
On Tue, 6 Aug 2013 09:14:05 +0800 Dong Wu <archer.wudong@gmail.com> wrote:
> Hi all, I have some questions about raid1 superblock and bad block.
> When I create raid1 with two disks, the md will write superblock to
> the disk, if the location of superblock is bad, what will happens?
The drive will be removed from the array.
> Just report create error or add the block to bad-block-list and
> redirect superblock to another place?
No. That would be nice but it isn't implemented.
> another question, how many bad blocks can be added to bad-block-list,
> when the bad-block-list is full, the raid will degrade?
512 ranges of badblocks. When it is full the array will degrade.
NeilBrown
>
> Thand you
>
> Wu Dong
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-06 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 1:14 when md raid1 superblock is bad block, what happens Dong Wu
2013-08-06 1:47 ` NeilBrown [this message]
2013-08-06 3:20 ` Roberto Spadim
-- strict thread matches above, loose matches on Subject: below --
2013-08-05 9:25 archer.wudong
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=20130806114707.0c3ffc07@notabene.brown \
--to=neilb@suse.de \
--cc=archer.wudong@gmail.com \
--cc=linux-raid@vger.kernel.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.