From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove to smaller PVs
Date: Thu, 27 Apr 2006 12:39:29 +0200 [thread overview]
Message-ID: <44509F61.1010501@conterra.de> (raw)
In-Reply-To: <20060405174425.GX4197@agk.surrey.redhat.com>
Alasdair G Kergon wrote:
> On Wed, Apr 05, 2006 at 07:34:18PM +0200, Fredrik Tolf wrote:
>> Can pvmove not just divide that storage into three "partitions",
>
> There's no logic to do that yet. It can only move complete sets of
> contiguous extents.
>
>> Is there a way for me to tell it to do so?
>
> As you found: break up contiguous extents explicitly on
> the command line by telling it to move smaller parts that it
> can handle.
I run into the same problem: I got a hw-raid controller and merged
all my individual disks into a raid5. Thus I got one big PV instead
of several small one. After moving back and forth some lvs, my PV
gets more and more fragmented. Thus I have to instruct pvmove
explicitly which fragments have to move.
The pvmove manpage explains shortly how pvmove works: Segments to
to move are added to a temporary 'pvmove' lv, but it seems lvmove
won't split any source segment into smaller pieces to fit into
any target segment. I may explicitly express source segments
(using :PE-PE), but this also becomes complicated if my source PV
is fragmented, too. Even if I do so, it is not clear to me, how
to express such a fragmented pvmove with a single command. Else
I have to perform lots of single pvmoves and have to wait for each
to become ready?
Dieter.
prev parent reply other threads:[~2006-04-27 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 17:34 [linux-lvm] pvmove to smaller PVs Fredrik Tolf
2006-04-05 17:44 ` Alasdair G Kergon
2006-04-05 17:57 ` Matt P
2006-04-05 17:58 ` Fredrik Tolf
2006-04-05 18:03 ` Alasdair G Kergon
2006-04-05 18:30 ` Fredrik Tolf
2006-04-27 10:39 ` Dieter Stüken [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=44509F61.1010501@conterra.de \
--to=stueken@conterra.de \
--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 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).