linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Heinz <oheinz@fbihome.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multipath problem [zero Block multipath device creation with mdadm 1.8.1]
Date: Thu, 25 Nov 2004 10:43:53 +0100	[thread overview]
Message-ID: <41A5A959.2050201@fbihome.de> (raw)
In-Reply-To: <20041123201650.GA8972@percy.comedia.it>

Luca Berra schrieb:

> On Tue, Nov 23, 2004 at 01:19:51PM +0100, Oliver Heinz wrote:
>
>> Mixing mdadm-1.6 and 1.8.1 for creating/managing the device doesn't 
>> work, it gives me an segfault.
>
>
> try patching mdadm-1.8.1 with this patch, it might help with the
> segfault.

This works! Thanks a lot!

Now creating the md-device with versions prior 1.8.1 works (I tested 
1.60 and 1.8.0) - restarting the array with them fails.
With 1.8.1 (with patch applied) I get an 0 Block device created bit I 
can restart the (correct) device I created with 1.60.

Now of course it would be great to get the device created and restarted 
with the same utility. We'd like to use it in production environment 
here, can more experienced mdadm users recommend that, these problems  
did not really strengthen our confidence in mdadm (at least when it 
comes to multipath, we have (of course) been using mdadm successfully 
for raid on severall systems).

Are the code changes in 1.8.1 so drastic that you would recommend to 
stick with prior versions and fix the issue with starting the array or 
would you suggest to get 1.8.1 to get MD creation in 1.8.1 fixed (well 
it need's to be fixed anyway ;-).

Bye,
Oliver


>
>
>------------------------------------------------------------------------
>
>--- mdadm-1.8.1/mdadm.c.bluca	2004-11-14 19:44:26.000000000 +0100
>+++ mdadm-1.8.1/mdadm.c	2004-11-14 19:44:31.747309097 +0100
>@@ -80,11 +80,10 @@
> 
> 	int mdfd = -1;
> 
>-	ident.uuid_set=0;
>+	memset(&ident,0,sizeof(struct mddev_ident_s));
> 	ident.level = UnSet;
> 	ident.raid_disks = UnSet;
> 	ident.super_minor= UnSet;
>-	ident.devices=0;
> 
> 	while ((option_index = -1) ,
> 	       (opt=getopt_long(argc, argv,
>--- mdadm-1.8.1/config.c.bluca	2004-11-02 06:11:06.000000000 +0100
>+++ mdadm-1.8.1/config.c	2004-11-14 19:44:35.693660204 +0100
>@@ -266,15 +266,11 @@
> 	struct mddev_ident_s mis;
> 	mddev_ident_t mi;
> 
>-	mis.uuid_set = 0;
>+	memset(&mis,0,sizeof(struct mddev_ident_s));
> 	mis.super_minor = UnSet;
> 	mis.level = UnSet;
> 	mis.raid_disks = UnSet;
> 	mis.spare_disks = UnSet;
>-	mis.devices = NULL;
>-	mis.devname = NULL;
>-	mis.spare_group = NULL;
>-	mis.autof = 0;
> 
> 	for (w=dl_next(line); w!=line; w=dl_next(w)) {
> 		if (w[0] == '/') {
>  
>
.

  reply	other threads:[~2004-11-25  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 12:19 Multipath problem Oliver Heinz
2004-11-23 20:16 ` Luca Berra
2004-11-25  9:43   ` Oliver Heinz [this message]
2004-11-30  2:44 ` Neil Brown

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=41A5A959.2050201@fbihome.de \
    --to=oheinz@fbihome.de \
    --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).