|
Bugzilla – Full Text Bug Listing |
| Summary: | Fails to create LVM volume if lvm+RAID1 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Max Lin <mlin> |
| Component: | Basesystem | Assignee: | heming zhao <heming.zhao> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | aschnell, ghe, reset11 |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Max Lin
2018-06-13 10:38:52 UTC
This looks like a problem of LVM. Since the devices /dev/vda2, /dev/vdb2, /dev/vdc2 and /dev/vdd2 are used by /dev/md0 LVM should not scan them for PVs. I was able to reproduce the issue without using YaST on the ISO used by openQA (20180680) but not older onces (e.g. 20180606). Hello Guys, The problem is a known issue for our current lvm2 code (2.02.177), due to spec file split. please see the similar bug https://bugzilla.suse.com/show_bug.cgi?id=1091863 We have found the root cause, but we need to work with the build team to solve this issue. Thanks Gang I assume this bug also prevents my machine from booting at all. OpenSuSE is installed on a raid1 with lvm ontop. The machine does not boot: "Cannot activate LVs in VG vghome while PVs appear on duplicate devices" Are there any workarounds known for the boot process to activate the pvm - as I am not able to boot my machine running lvm ontop raid1? in rdsosreport.txt I find: "Cannot activate LVs in VG vghome while PVs appear on duplicate devices." Hello Max, Arvin, Michael and Oliver, The bug is " failed to create LVM volume on top of raid1", right? When did you encounter this problem? what is the lvm2 version? Thanks Gang This is happened on openQA a while ago, can not see this issue on Tumbleweed nowadays. Assign this bug to Heming to follow up. For comment #8, close this bug as WONTFIX. |