From: martin f krafft <madduck@madduck.net>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Extending a 4×3Tb RAID10
Date: Tue, 9 Jul 2013 20:22:22 +0200 [thread overview]
Message-ID: <20130709182222.GA3952@fishbowl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Hello,
We have a RAID10 across 4 3TB drives (metadata version 1.2,
2 offset-copies, bitmaps), with LVM on top. We are running out of
space, but we don't really want to invest in 4 new 4TB drives right
now.
Is it possible to replace only two of the 3TB drives with 4TB drives
and get an extra terrabyte into the array somehow?
Anything I tried so far on a test system didn't work. I can add the
new devices to the RAID, but if I try to grow the array to the new
size, I get:
mdadm: component size of /dev/md2 unchanged at X
Do I have to fail two drives, create a new RAID10, add a new LVM PV
on it, and pvmove the data over, all the while hoping that none of
the four disks die — even though there is a backup (the two failed
drives), that's a one-shot backup and that is too risky.
That said, it isn't even possible to have a RAID10 across 2x2 pairs
of disks with different sizes, is it? Why not? I'd really rather
avoid pulling two RAID1s together with LVM, although I guess that is
essentially the same as RAID10.
Thanks,
--
martin | http://madduck.net/ | http://two.sentenc.es/
"the pure and simple truth is rarely pure and never simple."
-- oscar wilde
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) --]
[-- Type: application/pgp-signature, Size: 1124 bytes --]
next reply other threads:[~2013-07-09 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 18:22 martin f krafft [this message]
2013-07-09 21:24 ` Extending a 4×3Tb RAID10 NeilBrown
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=20130709182222.GA3952@fishbowl \
--to=madduck@madduck.net \
--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).