From: Wols Lists <antlists@youngman.org.uk>
To: Jack Wang <jack.wang.usish@gmail.com>,
Benjammin2068 <benjammin2068@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Using mdadm --grow to resize a RAID1
Date: Mon, 2 Jan 2017 16:19:27 +0000 [thread overview]
Message-ID: <586A7D8F.2060801@youngman.org.uk> (raw)
In-Reply-To: <CA+res+RgdS92HZ7ZQEs_D8TrQntuhGW-UYEjjARoxeJHKEZhZw@mail.gmail.com>
On 02/01/17 16:14, Jack Wang wrote:
> 2017-01-02 16:55 GMT+01:00 Benjammin2068 <benjammin2068@gmail.com>:
>>
>>
>> On 01/02/2017 06:19 AM, Wols Lists wrote:
>>> On 02/01/17 10:18, Benjammin2068 wrote:
>>>> I get stuck at the --size max.
>>>>
>>>> it seems the correct syntax is "--size=" but that "max" is not supported as an argument.
>>>>
>>>> little help?
>>> Off the top of my head - try with no argument. iirc it defaults to max,
>>> you don't need to tell it.
>>>
>>
>> Did that.
>>
>>
>>> [root@quantum ~]# mdadm --grow /dev/md1
>>> mdadm: no changes to --grow
>>
>>> [root@quantum ~]# mdadm --grow /dev/md1 --size
>>> mdadm: option '--size' requires an argument
>>> Usage: mdadm --help
>>> for help
>>
>>> [root@quantum ~]# mdadm --grow /dev/md1 --size max
>>> mdadm: component size of /dev/md1 unchanged at 239490048K
>>
>>> [root@quantum ~]# mdadm --grow /dev/md1 --size=max
>>> mdadm: component size of /dev/md1 unchanged at 239490048K
>
> So we need someone who has edit permission to update the the wiki page
> in https://raid.wiki.kernel.org/index.php/Growing
>
I've just checked the wiki page - it's not one of the ones I've yet
updated. I will be only too happy to do so, as soon as we can work out
(or someone tells us) the correct syntax to do so.
I must admit, using "man mdadm", it looks like Benjammin is doing the
right thing, so something's not quite right here ...
Cheers,
Wol
next prev parent reply other threads:[~2017-01-02 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 10:18 Using mdadm --grow to resize a RAID1 Benjammin2068
2017-01-02 12:19 ` Wols Lists
2017-01-02 15:55 ` Benjammin2068
2017-01-02 16:14 ` Jack Wang
2017-01-02 16:19 ` Wols Lists [this message]
2017-01-02 16:24 ` Roman Mamedov
2017-01-02 16:38 ` Benjammin2068
2017-01-02 17:59 ` Ben Kamen
2017-01-02 18:17 ` Wols Lists
2017-01-02 18:38 ` Ben Kamen
2017-01-02 18:52 ` Wols Lists
2017-01-02 19:11 ` Ben Kamen
2017-01-03 1:57 ` Ben Kamen
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=586A7D8F.2060801@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=benjammin2068@gmail.com \
--cc=jack.wang.usish@gmail.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).