From: Chase Venters <chase.venters@clientec.com>
To: Juraj Holtak <juraj@proaut.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: how to add third drive to RAID1 made of two drives without destroying data
Date: Sat, 22 Oct 2005 13:18:59 -0500 [thread overview]
Message-ID: <200510221319.22002.chase.venters@clientec.com> (raw)
In-Reply-To: <1129999982.11518.18.camel@localhost.localdomain>
On Saturday 22 October 2005 11:52 am, Juraj Holtak wrote:
> I know I can use the "new" drive I bought today as spare, but I really
> miss the point of a spare for raid1. I think, it makes much more sense,
> to build in the drive as a live one, so instead of RAID1 made of 2
> drives, I`ll get RAID1 made of 3 drives.
>
> I use mdadm to manage the drives. If I use --manage --add and add the
> drive(partition) to the array, it becomes a spare disk and this is not
> what I want it to do.
>
> Is there a way to upgrade my raid, without destroying data?
Indeed. Check mdadm --grow:
Usage: mdadm --grow device options
This usage causes mdadm to attempt to reconfigure a running array.
This is only possibly if the kernel being used supports a particular
reconfiguration. This version only supports changing the number of
devices in a RAID1, and changing the active size of all devices in
a RAID1/4/5/6.
Options that are valid with the grow (-G --grow) mode are:
--size= -z : Change the active size of devices in an array.
: This is useful if all devices have been replaced
: with larger devices.
--raid-disks= -n : Change the number of active devices in a RAID1
: array.
I haven't done it before personally, but I'd imagine:
mdadm --grow /dev/md0 --raid-disks=3
would be a good start (if not the total solution).
Cheers,
Chase
next prev parent reply other threads:[~2005-10-22 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 16:53 how to add third drive to RAID1 made of two drives without destroying data Juraj Holtak
2005-10-22 18:18 ` Chase Venters [this message]
2005-10-22 18:59 ` Juraj Holtak
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=200510221319.22002.chase.venters@clientec.com \
--to=chase.venters@clientec.com \
--cc=juraj@proaut.org \
--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 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.