From: Sarah Newman <srn@prgmr.com>
To: NeilBrown <nfbrown@novell.com>, linux-raid@vger.kernel.org
Subject: Re: mdadm bad blocks list
Date: Mon, 1 Feb 2016 18:40:43 -0800 [thread overview]
Message-ID: <56B0172B.8020808@prgmr.com> (raw)
In-Reply-To: <87twly1jc7.fsf@notabene.neil.brown.name>
On 01/27/2016 07:19 PM, NeilBrown wrote:
> On Thu, Jan 28 2016, Sarah Newman wrote:
>
>> Kernel: CentOS 6 Xen4CentOS 3.18.21-17
>> mdadm: CentOS 6 v3.3.2
>>
>> With the above behavior, I consider the bad blocks list to be actively harmful. If it's expected behavior in the current version, please consider
>> disabling the bad blocks list by default.
>
> You can do this yourself by putting
>
> CREATE bbl=no
>
> in /etc/mdadm.conf. That doesn't help others though.
FYI, I tried adding that line and if it is present when trying to add to an array that currently has a bad blocks list, I get the error message
md: sdi1 does not have a valid v1.0 superblock, not importing!
Is this expected?
Thanks, Sarah
next prev parent reply other threads:[~2016-02-02 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:45 mdadm bad blocks list Sarah Newman
2016-01-28 3:19 ` NeilBrown
2016-01-28 3:55 ` Sarah Newman
2016-01-28 4:45 ` NeilBrown
2016-01-30 18:22 ` Sarah Newman
2016-01-28 11:41 ` deprecating /proc/mdstat (was: Re: mdadm bad blocks list) Jens-U. Mozdzen
2016-01-28 18:21 ` Shaohua Li
2016-02-02 14:33 ` deprecating /proc/mdstat Jes Sorensen
2016-02-02 2:40 ` Sarah Newman [this message]
2016-02-11 4:15 ` mdadm bad blocks list NeilBrown
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=56B0172B.8020808@prgmr.com \
--to=srn@prgmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=nfbrown@novell.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.