From: Another Sillyname <anothersname@googlemail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Migrating a RAID 5 from 4x2TB to 3x6TB ?
Date: Tue, 9 Jun 2015 20:06:43 +0100 [thread overview]
Message-ID: <CAOS+5GG+qUz4No+Cur5_EEdv8ssAXzy41bFw524uEN9zpt-qKQ@mail.gmail.com> (raw)
In-Reply-To: <55773493.3050605@youngman.org.uk>
If you can try to pick up a cheap IBM M1015 Raid controller that you
can configure as JBOD (look to pay no more then £50 or $75).
Flash it to the standard LSI firmware (google M1015 LSI
firmware...there's plenty of forum pages on this).
Add your new drives to this controller, build new raid on this new
controller......copy dataset from old array.
I personally would NEVER suggest doing a migrate of drives or data
sizes on an active live dataset...if anything goes wrong you could
easily kill your data and have no backup.
On 9 June 2015 at 19:46, Wols Lists <antlists@youngman.org.uk> wrote:
> On 09/06/15 06:23, Can Jeuleers wrote:
>> On 08/06/15 21:28, Pierre Wieser wrote:
>>> Hi all,
>>>
>>> I currently have an almost full RAID 5 built with 4 x 2 TB disks.
>>> I wonder if it would be possible to migrate it to a bigger RAID 5
>>> with 3 x 6TB new disks.
>>
>> I'd recommend against it:
>>
>> https://en.wikipedia.org/wiki/RAID#Unrecoverable_read_errors_during_rebuild
>>
>> Jan
>>
> Please expand! Having read the article, it doesn't seem to say anything
> more than what is repeated time and time on this list - MAKE SURE YOUR
> DRIVES ARE DECENT RAID DRIVES.
>
> If you have ERC, then the odd "soft" read error doesn't matter. If you
> don't have ERC, then your data is at risk when you replace a drive, and
> it doesn't matter how big your drives are, it's the array size that matters.
>
> Cheers,
> Wol
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-09 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1419435054.589.1433790714774.JavaMail.zimbra@wieser.fr>
2015-06-08 19:28 ` Migrating a RAID 5 from 4x2TB to 3x6TB ? Pierre Wieser
2015-06-08 20:10 ` Wols Lists
2015-06-09 18:33 ` Pierre Wieser
2015-06-09 5:23 ` Can Jeuleers
2015-06-09 18:46 ` Pierre Wieser
2015-06-09 19:06 ` Wols Lists
2015-06-09 19:15 ` Roman Mamedov
2015-06-09 18:46 ` Wols Lists
2015-06-09 19:06 ` Another Sillyname [this message]
2015-06-09 19:18 ` Can Jeuleers
2015-06-15 11:31 ` Wilson, Jonathan
[not found] ` <CAOS+5GHzBgx2DuDe0+RLgZj9Q1BZ944i-9q4NEERq66Sk78b2g@mail.gmail.com>
2015-06-09 18:26 ` Pierre Wieser
2015-06-10 19:37 ` Pierre Wieser
2015-06-15 10:46 ` Wilson, Jonathan
2015-06-15 21:45 ` Wols Lists
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=CAOS+5GG+qUz4No+Cur5_EEdv8ssAXzy41bFw524uEN9zpt-qKQ@mail.gmail.com \
--to=anothersname@googlemail.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).