From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: [PATCH lvconvert 0/6] Refactoring lvconvert mirror
Date: Thu, 13 Dec 2007 16:05:08 -0500 [thread overview]
Message-ID: <47619E84.2060905@ce.jp.nec.com> (raw)
Hi,
This patchset refactors lvconvert mirror.
The patches are applicable on top of the pvmove refactoring patches.
https://www.redhat.com/archives/lvm-devel/2007-December/msg00020.html
I would like to know whether this changes are acceptable.
I guess there might be other needs for layer insertion/removal
APIs. Comments are welcome.
If they looks ok, I'll convert add-mirror-to-mirror patches based
on this.
The patches add following APIs:
- lv_add_mirrors(), lv_remove_mirrors()
Generic APIs for lvconvert mirror.
Having 2 modes of conversion: MIRROR_BY_SEG and MIRROR_BY_LV.
MIRROR_BY_LV is for the current version of lvconvert,
i.e. mirroring by mimage LVs.
MIRROR_BY_SEG is for the current version of pvmove,
i.e. mirroring segment by segment.
- add_mirror_images()
Add mirrors (mimage LVs) to LV.
The counter part of existing remove_mirror_images().
Wrapped by lv_add_mirrors().
- add_mirror_log(), remove_mirror_log()
Simplified version of the APIs specific to add/remove disk log.
- lv_mirror_count()
Returns the number of mirrors
- insert_layer_for_lv(), remove_layer_from_lv()
Insert a layer on top of the LV and remove it.
Then, lvconvert, lvcreate and pvmove are converted to use them.
The patchset also includes an experimental patch to allow
- lvcreate/lvconvert to create segment-by-segment mirrored LV
- pvmove to use disk log
[1/6] add insert_layer_for_lv() / remove_layer_from_lv()
[2/6] add add_mirror_images(), {add,remove}_mirror_log()
[3/6] change lvconvert to use the new APIs
[4/6] change lvcreate to use the new APIs
[5/6] remove unused mirror functions
[6/6] add and convert tools to use lv_{add,remove}_mirrors()
[Appendix] experimental: pvmove with disk log and seg-by-seg mirror LV
Thanks,
--
Jun'ichi Nomura, NEC Corporation of America
next reply other threads:[~2007-12-13 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 21:05 Jun'ichi Nomura [this message]
2007-12-13 21:31 ` [PATCH lvconvert 1/6] Add insert_layer_for_lv() / remove_layer_from_lv() Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 2/6] Add add_mirror_images() / {add, remove}_mirror_log() Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 3/6] Change lvconvert to use the new mirror APIs Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 4/6] Change lvcreate " Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 5/6] Remove unused mirror functions Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 6/6] Add lv_{add,remove}_mirrors() Jun'ichi Nomura
2007-12-13 21:32 ` [PATCH lvconvert Appendix] Experimental: pvmove with disk log and seg-by-seg mirrored LV 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=47619E84.2060905@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.