From: Phil Turmel <philip@turmel.org>
To: "Mathias Burén" <mathias.buren@gmail.com>,
"Wilson Jonathan" <piercing_male@hotmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: MD on raw device, use unallocated space anyway?
Date: Fri, 10 Jan 2014 18:19:01 -0500 [thread overview]
Message-ID: <52D07FE5.1030703@turmel.org> (raw)
In-Reply-To: <CADNH=7E3X7nbNC333==kN4X51=jAGJ4gF+qC_OX1uJ=GyUmR=g@mail.gmail.com>
On 01/10/2014 03:38 PM, Mathias Burén wrote:
> On 10 January 2014 20:10, Wilson Jonathan <piercing_male@hotmail.com> wrote:
>>
>> In that case the answer would be no. However if fail/remove the 3TB
>> drive, then partitioned the drive as 2TB and 1TB and then added the 2TB
>> partition back into the array then you can use the 1TB on its own...
>> just as long the "2TB" partition is the same size as the 2TB drives (or
>> slightly bigger) then it should all work nicely.
>
> Thanks, that confirms my suspicions. I wanted to avoid this (as a
> rebuild would be required) but it's the only way, I suppose.
Actually, you could move the data currently starting at sector zero to
sector 2048 (1MB) or some other start point, then partition the drive to
point at it. If your array has a bitmap, then you could quickly
--re-add the partition to the array.
> Unless I
> upgrade to 3TB all around and gain some storage.
Can't beat that. :-)
Phil
--
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
prev parent reply other threads:[~2014-01-10 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 17:36 MD on raw device, use unallocated space anyway? Mathias Burén
2014-01-10 18:12 ` Wilson Jonathan
2014-01-10 19:52 ` Mathias Burén
2014-01-10 20:10 ` Wilson Jonathan
2014-01-10 20:38 ` Mathias Burén
2014-01-10 21:59 ` Wilson Jonathan
2014-01-10 23:19 ` Phil Turmel [this message]
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=52D07FE5.1030703@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=piercing_male@hotmail.com \
/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).