Bug 638188
| Summary: | RFE: Provide a way to lazily clone an LV | ||
|---|---|---|---|
| Product: | [Community] LVM and device-mapper | Reporter: | Richard W.M. Jones <rjones> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| lvm2 sub component: | Changing Logical Volumes | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | medium | ||
| Priority: | low | CC: | agk, bmarzins, bmr, dwysocha, heinzm, jbrassow, jonathan, jpriddy, lvm-team, msnitzer, prajnoha, prockai, zkabelac |
| Version: | 2.02.166 | Flags: | rule-engine:
lvm-technical-solution?
rule-engine: lvm-test-coverage? |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-07-21 20:09:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Richard W.M. Jones
2010-09-28 13:16:33 UTC
I forgot - Jon already did this! To clone vg1/lvol0 to vg1/lvol2 try: lvconvert -m1 /dev/vg1/lvol0 lvconvert --splitmirrors 1 -n lvol2 /dev/vg1/lvol0 Then if you don't want to wait, we need to add a snapshot to the --splitmirrors mechanism, that disappears when it's complete. That's great. Is this available in a form that we can use now (with the mechanism hidden inside a "virt-clone"- type tool)? Is it worth combining the sequence into another script/command? Else I guess we can close this. (In reply to comment #8) > Is it worth combining the sequence into another script/command? Yes! lvclone ...? This bug should probably get closed.. very niche usecase that is unnecessary to do as suggested (with a "lazy clone"). I'd suggest using thinp: 1) either from the start, and then you'll be able to do highly scalable snapshots of snapshots, etc. 2) use an external origin with thinp -- this is useful if you have old logical volumes that you'd like to be able to snapshot (also capable of snapshots of snapshots). Closing (we now have this, its called: LVM thin provisioning, we didn't quite have it back in 2011 when this BZ was opened) |