From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Convert striped lv to single pv on another disk?
Date: Fri, 14 Dec 2012 13:33:09 -0500 [thread overview]
Message-ID: <50CB70E5.6010002@bmsi.com> (raw)
In-Reply-To: <50CA0492.1050906@redhat.com>
On 12/13/2012 11:38 AM, Bryn M. Reeves expounded in part:
> On 13/12/12 16:11, Gianluca Cecchi wrote:
>> I found in another thread that the resulting LV with pvmove remains a
>> striped one on only one disk as far as its structure is concerned...
>> with degraded performance...
>> Have you an example of pvmove command options to test to execute based
>> on my test?
>> So that I can verify with my loop devices?
> Yes, you're right. You will end up with both stripes still present but
> on a single disk.
>
> The best I could do using pvmove was to move individual extents around
> (!) to make the LV contiguous on-disk. Of course, this doesn't remove
> the striping and inflates the number of segments since each pair of
> striped extents effectively becomes a segment.
>
> The lvconvert command also still accepts a -i <n> parameter but doesn't
> do anything useful with it and doesn't report an error.
>
Could you create an asymmetrical mirror - where one leg is striped and
the other is linear? Then you can just sync the mirror and delete the
striped leg. I could even see operating with such a mirror - call it
RAID �. Reads would prefer the striped side, and the mirror is there in
case one of the stripes fails, while requiring only 1 additional drive
and degrading only write performance.
RAID10 over the 3 drives is probably better, though.
prev parent reply other threads:[~2012-12-14 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 13:32 [linux-lvm] Convert striped lv to single pv on another disk? Gianluca Cecchi
2012-12-13 15:28 ` Gianluca Cecchi
2012-12-13 15:39 ` Bryn M. Reeves
2012-12-13 16:11 ` Gianluca Cecchi
2012-12-13 16:38 ` Bryn M. Reeves
2012-12-14 18:33 ` Stuart D Gathman [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=50CB70E5.6010002@bmsi.com \
--to=stuart@bmsi.com \
--cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.