From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: Multipath problem
Date: Tue, 23 Nov 2004 21:16:51 +0100 [thread overview]
Message-ID: <20041123201650.GA8972@percy.comedia.it> (raw)
In-Reply-To: <41A32AE7.2080502@fbihome.de>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
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.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
[-- Attachment #2: mdadm-1.8.1-memset.patch --]
[-- Type: text/plain, Size: 933 bytes --]
--- 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] == '/') {
next prev parent reply other threads:[~2004-11-23 20:16 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 [this message]
2004-11-25 9:43 ` Multipath problem [zero Block multipath device creation with mdadm 1.8.1] Oliver Heinz
2004-11-30 2:44 ` Multipath problem 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=20041123201650.GA8972@percy.comedia.it \
--to=bluca@comedia.it \
--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).