Bug 836720
Summary: | LVMcache currently calls lvm pvs with each pv as an argument, this can lead to inconsistent results if the first pv does not hold an active mda (LVM BZ#83663) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Lee Yarwood <lyarwood> |
Component: | vdsm | Assignee: | Eduardo Warszawski <ewarszaw> |
Status: | CLOSED DUPLICATE | QA Contact: | Haim <hateya> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.3 | CC: | abaron, bazulay, iheim, mkalinin, sputhenp, yeylon, ykaul |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | storage | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-07-03 15:32:05 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: | 836663 | ||
Bug Blocks: | 759131 |
Description
Lee Yarwood
2012-06-30 11:19:15 UTC
Haim, there is something I don't understand here. In V2 storage domains we store this info for BC purposes only, but functionally this should not affect anything. Can you get a MetaDataMappingError using V2? My limited testing today against V2 domains with missing MDT_PVn lines appears to confirm that they are not impacted by this. I was able to create a vdisk with it's LV spanning multiple PVs without any errors being reported. # lvs -o seg_all 480a7532-cf70-4fc3-9341-65b9f3a0fa19/7490f674-1878-4b48-96c4-dedae978b28c Type #Str Stripe Stripe Region Region Chunk Chunk Start Start SSize Seg Tags PE Ranges Devices linear 1 0 0 0 0 0 0 0 0 24.62g /dev/mapper/1IET_0001000a:0-196 /dev/mapper/1IET_0001000a(0) linear 1 0 0 0 0 0 0 24.62g 197 24.62g /dev/mapper/1IET_00010009:0-196 /dev/mapper/1IET_00010009(0) linear 1 0 0 0 0 0 0 49.25g 394 24.62g /dev/mapper/1IET_00010001:0-196 /dev/mapper/1IET_00010001(0) linear 1 0 0 0 0 0 0 73.88g 591 24.62g /dev/mapper/1IET_00010004:0-196 /dev/mapper/1IET_00010004(0) linear 1 0 0 0 0 0 0 98.50g 788 1.50g /dev/mapper/1IET_00010002:71-82 /dev/mapper/1IET_00010002(71) *** This bug has been marked as a duplicate of bug 798635 *** |