From: Dan Williams <dan.j.williams@intel.com>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org,
ed.ciechanowski@intel.com, marcin.labun@intel.com
Subject: Re: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
Date: Tue, 29 Nov 2011 18:30:52 -0800 [thread overview]
Message-ID: <CAA9_cmdeSfx6dZVwUZ-00mLfFAi+PPKcGCDLBpB8icA5BS4j6g@mail.gmail.com> (raw)
In-Reply-To: <20111124121718.5254.16301.stgit@gklab-128-013.igk.intel.com>
On Thu, Nov 24, 2011 at 4:17 AM, Adam Kwolek <adam.kwolek@intel.com> wrote:
> When 2 maps are present, IMSM can use shorter map for setting disk
> in to degraded state. It can happen that degraded disk can be not present
> in shorter map.
> We should use longer map for setting disk in to degraded state.
I don't understand this patch. If we are setting a new degraded disk
migration is idle and the degraded state is set in map[0].
--
Dan
next prev parent reply other threads:[~2011-11-30 2:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 12:17 [PATCH 00/11] Degradation during reshape Adam Kwolek
2011-11-24 12:17 ` [PATCH 01/11] imsm: FIX: Return longer map for failure setting Adam Kwolek
2011-11-30 2:30 ` Dan Williams [this message]
2011-11-30 7:56 ` Kwolek, Adam
2011-11-30 15:37 ` Williams, Dan J
2011-12-01 7:54 ` Kwolek, Adam
2011-11-24 12:17 ` [PATCH 02/11] imsm: FIX: Mark both maps on degradation while migrating Adam Kwolek
2011-11-24 12:17 ` [PATCH 03/11] imsm: FIX: Do not end migration when missing drive is handled Adam Kwolek
2011-11-24 12:17 ` [PATCH 04/11] imsm: FIX: Finalize degraded migration Adam Kwolek
2011-11-24 12:17 ` [PATCH 05/11] imsm: FIX: Remove single map state limitation in getinfo Adam Kwolek
2011-11-24 12:17 ` [PATCH 06/11] imsm: FIX: Restore critical section on degraded array Adam Kwolek
2011-11-24 12:18 ` [PATCH 07/11] imsm: FIX: Manage second map state on array degradation Adam Kwolek
2011-11-24 12:18 ` [PATCH 08/11] imsm: FIX: Function rework - imsm_count_failed() Adam Kwolek
2011-11-24 12:18 ` [PATCH 09/11] imsm: FIX: Check maximum allowed degradation level in open_backup_targets() Adam Kwolek
2011-11-24 12:18 ` [PATCH 10/11] imsm: FIX: Check maximum allowed degradation level in recover_backup_imsm() Adam Kwolek
2011-11-24 12:18 ` [PATCH 11/11] Disable BBM when it is not supported Adam Kwolek
2011-12-06 0:53 ` [PATCH 00/11] Degradation during reshape NeilBrown
2011-12-06 8:03 ` Kwolek, Adam
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=CAA9_cmdeSfx6dZVwUZ-00mLfFAi+PPKcGCDLBpB8icA5BS4j6g@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=adam.kwolek@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=marcin.labun@intel.com \
--cc=neilb@suse.de \
/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).