From: Stan Hoeppner <stan@hardwarefreak.com>
To: Rob Emanuele <rob@emanuele.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 10 Repairs
Date: Mon, 03 Jun 2013 00:13:51 -0500 [thread overview]
Message-ID: <51AC260F.8050806@hardwarefreak.com> (raw)
In-Reply-To: <CAE98Ua_Js7wpfkT7wAZhm79Y46t4Fqtfx3752SUO_+H-3jqqcQ@mail.gmail.com>
On 6/2/2013 9:07 PM, Rob Emanuele wrote:
> So, I've been looking at repairing my RAID 10 software array. I have a
> failing drive with incrementing SMART errors. I went to replace that
> drive with a new drive. The failing drive is 250,059,350,016 bytes
> while the batch of new drives I bought as spares are 250,000,000,000
> bytes.
>
> When I add the new drive it tells me the drive is too small. Is there
> a way to shrink the array so that new new drives (any any other
> replacement drives around 250G) will work in the array?
High Rob,
They're 250GB drives. Frankly what I'd do is get your investment back
from those 'new' drives, though it probably wasn't much if acquired
recently. Acquire a number of 750GB, 1TB drives that yield similar
total space after RAID10 overhead. Build a new array, mkfs, copy all
the data over, and decommission the old disks, then Ebay them.
Or just acquire two 2TB drives an mirror them. 20x 250GB drives in
RAID10 is 2.5TB net space. Surely you don't currently have 20 drives in
this RAID array. If you're acquiring 250GB drives in 2013 I'd guess
you're not after performance. So reducing spindle count shouldn't be an
issue, should it?
--
Stan
next prev parent reply other threads:[~2013-06-03 5:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 2:07 RAID 10 Repairs Rob Emanuele
2013-06-03 5:13 ` Stan Hoeppner [this message]
2013-06-08 17:35 ` Bill Davidsen
2013-06-08 23:28 ` Stan Hoeppner
2013-06-09 2:11 ` Bill Davidsen
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=51AC260F.8050806@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=rob@emanuele.us \
/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).