From: Roman Mamedov <rm@romanrm.ru>
To: linux-raid@vger.kernel.org
Subject: Reshape RAID5 to a RAID6 with more (smaller) devices
Date: Wed, 12 Jan 2011 12:29:30 +0500 [thread overview]
Message-ID: <20110112122930.6a17440f@natsu> (raw)
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
Hello!
I am considering to move my configuration in which I currently use two RAID5
arrays (3*2TB and 3*1TB) to one described in [1]. Specifically, make a 6*1TB
RAID6 plus 3*1TB RAID5 consisting of 2TB drives' "tails".
My question is: does mdadm support a simultaneous reshape, changing at once:
1) RAID5 to RAID6
2) number of devices from 3 to 6
3) individual device size from 2TB to 1TB
Note that the user-accessible space after this reshape does not change, and
remains at 4 TB. So is that supported? Will that require a backup file? Will
that proceed particularly inefficiently/slowly?
[1] http://www.linuxconfig.org/prouhd-raid-for-the-end-user
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-01-12 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 7:29 Roman Mamedov [this message]
2011-01-12 7:54 ` Reshape RAID5 to a RAID6 with more (smaller) devices 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=20110112122930.6a17440f@natsu \
--to=rm@romanrm.ru \
--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