Bug 1189108
| Summary: | LVM Cache: Ability to create thinsnap of cached external origin | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jonathan Earl Brassow <jbrassow> | ||||
| Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> | ||||
| lvm2 sub component: | Cache Logical Volumes | QA Contact: | cluster-qe <cluster-qe> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | Steven J. Levine <slevine> | ||||
| Severity: | unspecified | ||||||
| Priority: | unspecified | CC: | agk, cmarthal, coughlan, hartsjc, heinzm, jbrassow, loberman, msnitzer, nperic, pasik, prajnoha, rbednar, zkabelac | ||||
| Version: | 7.2 | Keywords: | FutureFeature | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | lvm2-2.02.169-1.el7 | Doc Type: | Release Note | ||||
| Doc Text: |
Support for thin snapshots of cached logical volumes
LVM in Red Hat Enterprise Linux 7.4 allows you to create thin snapshots of cached logical volumes. This feature was not available in earlier releases. These external origin cached logical volumes are converted to a read-only state and thus can be used by different thin pools.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1471212 (view as bug list) | Environment: | |||||
| Last Closed: | 2017-08-01 21:47:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1385242, 1471212 | ||||||
| Attachments: |
|
||||||
|
Description
Jonathan Earl Brassow
2015-02-04 13:23:57 UTC
Upstream patch (member of 2.02.169 release) https://www.redhat.com/archives/lvm-devel/2016-December/msg00101.html enabled support for using cache LV as external origin (together with surrounding patches to unable online caching & uncaching of existing external origin). Also (as it's using very similar dm tree handling) we enabled usage for 'old' snapshot of cache LV. Basically there is no extension to supported syntax, just accepts 'cache' type as accepted LV type for command. lvconvert --thin vg/cacheLV --originname extorigname --thinpool vg/pool - makes cacheLV -> cached external origin (read-only) and thinLV available to the user for read/write lvcreate -s -L1 vg/cacheLV - takes snapshot of cached LV which could be later dropped/merged lvconvert -s vg/cacheLV cowLV - recombine i.e. split snapshot back together with cached origin. Created attachment 1270433 [details]
test result
Verified. It is now possible to use cacheLV as external origin for thin snapshot.
Also added automated test coverage. External cache origin test will be now part of regression testing as well. Ext. cache variants also available for other scenarios which used non-cached ext. origin up until now.
Attaching test result logs for single node and cluster tests.
Unique test name for test execution via vedder added to QA whiteboard for reference.
3.10.0-640.el7.x86_64
lvm2-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
lvm2-libs-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
lvm2-cluster-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
device-mapper-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
device-mapper-libs-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
device-mapper-event-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
device-mapper-event-libs-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
device-mapper-persistent-data-0.7.0-0.1.rc6.el7 BUILT: Mon Mar 27 17:15:46 CEST 2017
cmirror-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
Adding summary for release note format, plus very slight edit of release note text. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2222 |