From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] pvmove doesn't work the way the man page says
Date: Fri, 15 Feb 2013 10:22:16 +0100 [thread overview]
Message-ID: <20130215092216.GD20791@soda.linbit> (raw)
In-Reply-To: <20130214005854.GF24130@agk-dp.fab.redhat.com>
On Thu, Feb 14, 2013 at 12:58:54AM +0000, Alasdair G Kergon wrote:
> On Thu, Feb 14, 2013 at 01:45:35AM +0100, Spelic wrote:
> > breaking it up in smaller subsegments would probably have been wiser,
>
> The plan was always for more frequent checkpoints, but it involves more
> complicated code and there's simply been no need to do this: given how rarely
> pvmove is used, the current approach seems to be good enough and nobody's
> written the extra code yet.
Also, if you want more frequent checkpoints,
you can do that by calling pvmove appropriately:
just don't move the whole thing at once,
but repeatedly call pvmove with an explicit extent range.
Lars
next prev parent reply other threads:[~2013-02-15 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 15:43 [linux-lvm] pvmove doesn't work the way the man page says Phillip Susi
2013-02-14 0:45 ` Spelic
2013-02-14 0:58 ` Alasdair G Kergon
2013-02-14 13:25 ` Marian Csontos
2013-02-14 13:41 ` Alasdair G Kergon
2013-02-14 16:54 ` Marian Csontos
2013-02-15 9:22 ` Lars Ellenberg [this message]
2013-03-09 18:04 ` Phillip Susi
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=20130215092216.GD20791@soda.linbit \
--to=lars.ellenberg@linbit.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 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).