From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, ed.ciechanowski@intel.com,
marcin.labun@intel.com, dan.j.williams@intel.com
Subject: Re: [PATCH] md: Add ability for disable bad block management
Date: Wed, 30 Nov 2011 11:14:03 +1100 [thread overview]
Message-ID: <20111130111403.7efd3875@notabene.brown> (raw)
In-Reply-To: <20111124121953.5509.28118.stgit@gklab-128-013.igk.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Thu, 24 Nov 2011 13:19:53 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> When external metadata doesn't support BBM, mdadm cannot answer correctly
> for BBM requests. It causes reshape process being stopped.
>
> Add ability for external metadata /mdadm/ to disable BBM via sysfs.
> md will ignore bad blocks as it is for metadata v0.90.
This should not be necessary.
The intention is that a device with a bad block looks exactly like a device
with a failed device. i.e. 'faulty' and 'blocked' appear in the 'state'
file.
If the metadata doesn't support a bad-block list, it will record that the
device has failed and will unblock the device. At that point the failure is
forced.
If the metadata does support a bad block list it will just record the bad
blocks and acknowledge them, and the unblock the device. At that point the
device won't be failed, the 'faulty' state will disappear, and it will
continue to be used with the known bad blocks.
What exactly is going wrong that makes you think you need this patch?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-11-30 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 12:19 [PATCH] md: Add ability for disable bad block management Adam Kwolek
2011-11-24 12:23 ` Paul Menzel
2011-11-24 12:28 ` Kwolek, Adam
2011-11-24 12:48 ` Paul Menzel
2011-11-30 0:14 ` NeilBrown [this message]
2011-11-30 8:17 ` Kwolek, Adam
2011-12-06 6:05 ` NeilBrown
2011-12-06 13:02 ` Kwolek, Adam
2011-12-07 1:52 ` NeilBrown
2011-12-07 11:10 ` Kwolek, Adam
2011-12-08 4:02 ` NeilBrown
2011-12-08 15:36 ` Kwolek, Adam
2011-12-09 3:53 ` 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=20111130111403.7efd3875@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=marcin.labun@intel.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).