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 0/9] Array degradation during reshape and rebuild (cont.)
Date: Thu, 8 Dec 2011 14:15:15 +1100 [thread overview]
Message-ID: <20111208141515.39ca955c@notabene.brown> (raw)
In-Reply-To: <20111207125549.25279.43741.stgit@gklab-128-013.igk.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Wed, 07 Dec 2011 13:57:35 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> The following series adds implementation details for array
> degradation during reshape and rebuild/initialization.
>
> Series fixes problems in handling degradation during rebuild
> in imsm metadata and fixes problems noticed in applied changes..
>
> Failing disks using sysfs (echo 1 > /sys/block/sdX/device/delete)
> mdadm does his job correctly.
> The problem is when disks are pulled physically from system.
> As workaround BBM disabling can be used /sent previously/.
>
>
> BR
> Adam
>
>
> ---
>
> Adam Kwolek (9):
> imsm: FIX: Use defines for device map access
> imsm: FIX: Check correct slots on disk failure
> imsm: FIX: Finish rebuild and initialization when missing drive is handled
> imsm: FIX: Mark failure for rebuild
> imsm: FIX: Add array map state transition for failures during initialization
> imsm: FIX: Do not allow spare activation during rebuild
> imsm: Function imsm_set_disk() rework
> imsm: FIX: Correct ords merging in end_migration()
> imsm: FIX: Remove longer map request
>
>
> super-intel.c | 475 ++++++++++++++++++++++++++++++++++-----------------------
> 1 files changed, 285 insertions(+), 190 deletions(-)
>
Thanks.
I've applied all of these.
I can't claim to have understood them all completely, but there was nothing
obviously wrong, so I'll assume they are right :-)
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2011-12-08 3:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 12:57 [PATCH 0/9] Array degradation during reshape and rebuild (cont.) Adam Kwolek
2011-12-07 12:57 ` [PATCH 1/9] imsm: FIX: Remove longer map request Adam Kwolek
2011-12-07 12:57 ` [PATCH 2/9] imsm: FIX: Correct ords merging in end_migration() Adam Kwolek
2011-12-07 12:57 ` [PATCH 3/9] imsm: Function imsm_set_disk() rework Adam Kwolek
2011-12-07 12:58 ` [PATCH 4/9] imsm: FIX: Do not allow spare activation during rebuild Adam Kwolek
2011-12-07 12:58 ` [PATCH 5/9] imsm: FIX: Add array map state transition for failures during initialization Adam Kwolek
2011-12-07 12:58 ` [PATCH 6/9] imsm: FIX: Mark failure for rebuild Adam Kwolek
2011-12-07 12:58 ` [PATCH 7/9] imsm: FIX: Finish rebuild and initialization when missing drive is handled Adam Kwolek
2011-12-07 12:58 ` [PATCH 8/9] imsm: FIX: Check correct slots on disk failure Adam Kwolek
2011-12-07 12:58 ` [PATCH 9/9] imsm: FIX: Use defines for device map access Adam Kwolek
2011-12-08 3:15 ` NeilBrown [this message]
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=20111208141515.39ca955c@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).