Bug 928997

Summary: Determine which LVM device types can be stacked, in which order.
Product: Red Hat Enterprise Linux 7 Reporter: Tom Coughlan <coughlan>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
lvm2 sub component: Default / Unclassified QA Contact: cluster-qe <cluster-qe>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: high CC: agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, thornber, zkabelac
Version: 7.0Keywords: Triaged
Target Milestone: beta   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-14 08:45:10 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:

Description Tom Coughlan 2013-03-28 23:59:19 UTC 
LVM has recently added several new device types based on dm-raid, thinp, thin snap, (and soon) dm-cache. These are in addition to linear, stripe, mirror. We also have crypt, multipath, and md outside LVM.  

We need to specify which combinations of these device types are allowed to be stacked, and in which order. Additional factors, like external origins, metadata, and log devices must be considered.  

Code may be required to disallow unsupported combinations.

Instructions for how to properly create these stacked devices needs to be included in the LVM documentation. 

Full testing of the allowed combinations needs to be included in the QE plan.
Comment 1 Zdenek Kabelac 2013-05-14 08:45:10 UTC 

*** This bug has been marked as a duplicate of bug 928996 ***