From: Neil Brown <neilb@suse.de>
To: Luca Berra <bluca@comedia.it>
Cc: "Marcin Mirosław" <marcin@mejor.pl>, linux-raid@vger.kernel.org
Subject: Re: mdadm-3.1.1 segfaults when mdadm -G -Z
Date: Mon, 1 Feb 2010 09:17:25 +1100 [thread overview]
Message-ID: <20100201091725.2023091c@notabene.brown> (raw)
In-Reply-To: <20100130095611.GC15471@maude.comedia.it>
On Sat, 30 Jan 2010 10:56:11 +0100
Luca Berra <bluca@comedia.it> wrote:
> On Sun, Jan 10, 2010 at 02:54:02PM +0100, Marcin Mirosław wrote:
> >W dniu 2010-01-10 14:47, Zdenek Behan pisze:
> >> -Z, --array-size=
> >> This is only meaningful with --grow and its effect is
> >> not per‐
> >> sistent: when the array is stopped an restarted the
> >> default
> >> array size will be restored.
> >
> >Yes, i missed it.
> >
> >> You didn't supply any argument to -Z at all, or to be precise, you
> >> supplied /dev/md6 as the argument, whereas you should have put in the
> >> array size.
> >>
> >> Also, another thing I have noticed lately is, that _some_ short options
> >> seem to be somehow oddly broken on my system and not accepting
> >> arguments, even if they are supposed to be. If the segfault persists
> >> after using the correct syntax, try using the long opts instead. I was
> >> planning to dig more into this bug myself, so I might just kick self to
> >> do it now.
> >
> >long option, with suplied array size works correctly, so indeed problem
> >is in short option.
> >Thank you!
> >Regards.
>
> attached patch fixes it.
Applied, thanks.
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-31 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 12:13 mdadm-3.1.1 segfaults when mdadm -G -Z Marcin Mirosław
2010-01-10 13:47 ` Zdenek Behan
2010-01-10 13:54 ` Marcin Mirosław
2010-01-30 9:56 ` Luca Berra
2010-01-31 22:17 ` Neil Brown [this message]
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=20100201091725.2023091c@notabene.brown \
--to=neilb@suse.de \
--cc=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
--cc=marcin@mejor.pl \
/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.