From: NeilBrown <neilb@suse.de>
To: "Czarnowska, Anna" <anna.czarnowska@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Labun, Marcin" <Marcin.Labun@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>
Subject: Re: [PATCH] imsm: do not fail load_container when first 2 disks are missing
Date: Tue, 6 Dec 2011 11:08:09 +1100 [thread overview]
Message-ID: <20111206110809.00828921@notabene.brown> (raw)
In-Reply-To: <3F8F31A3BFD1664EAB894D1BD6AF32B9053871@IRSMSX102.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]
On Thu, 24 Nov 2011 11:24:16 +0000 "Czarnowska, Anna"
<anna.czarnowska@intel.com> wrote:
> Failure to find migration record should not fail the whole load_container.
> It causes that degraded raid10 with first 2 disks missing cannot be assembled.
>
> Signed-off-by: Anna Czarnowska <anna.czarnowska@intel.com>
> ---
> super-intel.c | 10 ++--------
> 1 files changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/super-intel.c b/super-intel.c
> index a0672bf..21147c2 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -3953,15 +3953,9 @@ static int load_super_imsm_all(struct supertype *st, int fd, void **sbp,
> goto error;
> }
>
> - /* load migration record */
> - err = load_imsm_migr_rec(super, NULL);
> - if (err) {
> - err = 4;
> - goto error;
> - }
> -
> /* Check migration compatibility */
> - if (check_mpb_migr_compatibility(super) != 0) {
> + if (load_imsm_migr_rec(super, NULL) == 0 &&
> + check_mpb_migr_compatibility(super) != 0) {
> fprintf(stderr, Name ": Unsupported migration detected");
> if (devname)
> fprintf(stderr, " on %s\n", devname);
Sorry for the long delay in replying. The last two weeks have held lots of
interruptions and distractions.
There are two things about this that don't make sense to me. Perhaps you can
clarify.
Firstly, imsm raid10 only supports a 4-device layout with the first two
devices effectively mirrors, same for the second two, and data striped over
the 2 pairs. i.e. an 'n2' layout on 4 devices.
So if the first 2 disks are missing, then you have lost half your data and it
would be wrong to successfully assemble the array.
Secondly, if the migration record is missing, then presumably you do not know
the full state of the array so again - assembling the array would be wrong.
So I cannot see how this patch can be correct. If it is, please explain.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-12-06 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 11:24 [PATCH] imsm: do not fail load_container when first 2 disks are missing Czarnowska, Anna
2011-12-06 0:08 ` NeilBrown [this message]
2011-12-06 8:36 ` Czarnowska, Anna
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=20111206110809.00828921@notabene.brown \
--to=neilb@suse.de \
--cc=Marcin.Labun@intel.com \
--cc=anna.czarnowska@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
/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).