From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: Re: RAID-6 horizontal grow
Date: Sat, 11 Apr 2009 12:40:47 +0200 [thread overview]
Message-ID: <20090411104047.GA4489@lazy.lzy> (raw)
In-Reply-To: <bf90f0dca1b3c313c8ef5e74a4648938.squirrel@neil.brown.name>
Hi,
> I love it when people find out answers by themselves - it shows the
> documentation isn't completely worthless :-)
well, I think the mdadm man page is good and
complete, even if it requires several re-reads
in order to get all the information... :-)
It is definitely worth!
BTW, maybe it would be good to update the wiki
page about this topic.
> I think so, but mdadm cannot do it for you (yet).
>
> If you
> for i in /sys/block/mdX/md/dev-*/size
> do echo 0 > $i
> done
>
> it will have much the same effect as --assemble --update devicesize
Thank you so much!
This is exactly what I needed!
Thanks again,
bye,
--
piergiorgio
prev parent reply other threads:[~2009-04-11 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 21:54 RAID-6 horizontal grow Piergiorgio Sartor
2009-04-10 21:58 ` Robin Hill
2009-04-10 22:34 ` Piergiorgio Sartor
2009-04-11 8:23 ` Piergiorgio Sartor
2009-04-11 9:53 ` NeilBrown
2009-04-11 10:40 ` Piergiorgio Sartor [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=20090411104047.GA4489@lazy.lzy \
--to=piergiorgio.sartor@nexgo.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