From: Mike Hardy <mhardy@h3c.com>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm source rpm build error + command-line parsing error + resync reporting problem
Date: Thu, 08 Dec 2005 21:43:41 -0800 [thread overview]
Message-ID: <4399198D.5050206@h3c.com> (raw)
Neil Brown wrote:
>>The man page indicates that if I don't set the size, it will grow to
>>fill the smallest device in the array. It's definitely not doing
>>that...
>
>
> Could you please point me to the part of the man page that says that?
> I will try to fix it.
I see what you mean now - I got confused because there are two
paragraphs in the size option description, one indicates that you don't
need to set it, then the second paragraph discusses the "grow" context
and indicates you can use 'max'.
The first paragraph doesn't indicate a specific context, so I took it to
cover all possible contexts where 'size' was applicable, and it seems
like it isn't
I did successfully grow my md arrays though, which was nice, but then
ext2online didn't do what I asked it to do, and now I'm back to just
doing the more typical dump/restore thing anyway.
Not really on-topic, but has anyone else gotten ext2online to work? I
get this "Dec 8 21:27:02 istanbul kernel: JBD: ext2online wants too
many credits (2050 > 2048)" after letting it attempt to extend the FS to
cover the entire device.
-Mike
next reply other threads:[~2005-12-09 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 5:43 Mike Hardy [this message]
2005-12-09 5:55 ` mdadm source rpm build error + command-line parsing error + resync reporting problem Neil Brown
2005-12-09 6:31 ` Mike Hardy
-- strict thread matches above, loose matches on Subject: below --
2005-12-09 5:11 Mike Hardy
2005-12-09 5:16 ` Mike Hardy
2005-12-09 5:33 ` 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=4399198D.5050206@h3c.com \
--to=mhardy@h3c.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).