From: Lukasz Orlowski <lukasz.orlowski@intel.com>
To: neilb@suse.de, dan.j.williams@intel.com
Cc: linux-raid@vger.kernel.org
Subject: [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10
Date: Fri, 21 Oct 2011 09:47:29 +0200 [thread overview]
Message-ID: <20111021074643.14969.22068.stgit@gklab-128-192.igk.intel.com> (raw)
The following series fixes metadata updates handling code after migration from Raid 0 to Raid 10:
Last disk is left as a spare instead of being activated and a missing disk is a
member of an array instead of being removed. The array status is degraded
instead of normal.
---
Lukasz Orlowski (1):
imsm: Moves metadata update code for spare activation to separate function
Lukasz Orlowski (1):
imsm: fix: Fixes metadata after migration from Raid 0 to Raid 10
super-intel.c | 207 +++++++++++++++++++++++++++++++--------------------------
1 files changed, 114 insertions(+), 93 deletions(-)
--
Signature
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk
Sad Rejonowy Gdansk Polnoc w Gdansku,
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego,
numer KRS 101882
NIP 957-07-52-316
Kapital zakladowy 200.000 zl
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next reply other threads:[~2011-10-21 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 7:47 Lukasz Orlowski [this message]
2011-10-21 7:47 ` [PATCH 1/2] imsm: Moves metadata update code for spare activation to separate function Lukasz Orlowski
2011-10-21 7:47 ` [PATCH 2/2] imsm: fix: Fixes metadata after migration from Raid 0 to Raid 10 Lukasz Orlowski
2011-10-22 0:50 ` [PATCH 0/2] Fixes metadata while migrating " 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=20111021074643.14969.22068.stgit@gklab-128-192.igk.intel.com \
--to=lukasz.orlowski@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--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 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.