All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: [PATCH pvmove 2/3] support splitted destinations of pvmove
Date: Wed, 21 Nov 2007 16:28:02 -0500	[thread overview]
Message-ID: <4744A2E2.3070503@ce.jp.nec.com> (raw)
In-Reply-To: <4744A21E.7090601@ce.jp.nec.com>

Currently, pvmove can't split destination area.
This patch removes the restriction.
(Actually, a prepration for removing the restriction.)

If you have 1GB LV on a contiguous area of PV1
and would like to move it to 2 x 500MB PVs, PV2 and PV3,
you have to manually split the pvmove session into 2.

It's because pvmove assumes 1-1 relationship between
source area and destination area and forces a contiguous allocation.

This patch changes pvmove completion to split the original segment
to map to the destination areas.

Other patch ("3/3" of this series) allows allocation of splitted areas
for a single source area.

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-pvmove-handle-splitted-area.patch
Type: text/x-patch
Size: 1772 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20071121/0f07c413/attachment.bin>

  reply	other threads:[~2007-11-21 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 21:24 [PATCH pvmove 1/3] remove pvmove-specific params from allocation code Jun'ichi Nomura
2007-11-21 21:28 ` Jun'ichi Nomura [this message]
2007-11-21 21:28 ` [PATCH pvmove 3/3] use generic mirror allocation for pvmove Jun'ichi Nomura
2007-11-21 22:45 ` [PATCH pvmove appendix] 'make check' script for testing basic pvmove operations Jun'ichi Nomura

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=4744A2E2.3070503@ce.jp.nec.com \
    --to=j-nomura@ce.jp.nec.com \
    --cc=lvm-devel@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.