Bug 126565
Summary: | 2.6.6-435 causes problems with LVM2 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Heiko Jakob <buffalo> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | dkelson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-12-03 16:04:31 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
Heiko Jakob
2004-06-23 11:28:13 UTC
I did some further investigation on this problem and found out that: 2.6.5smp-358 has the same problem like 2.6.6smp-435 when not failing to locate PVs for Volume01. That means, that this bug is two bugs and it has only a few to do with raid5: 1.) the minor problem: Raid5 devices created under 2.6.6smp-435 won't work under 2.6.5-358. /proc/mdstat doesn't recognize them and the start of the Volumegroups containing raid 5 devices will fail. 2.) the major problem: Having / in a logical volume and more than 1 Volumegroup exists on the system will result in a report of a bad superblock on / during boot. It's not really a bad superblock, but fsck reports it and the boot procedure stops by dropping you on the password or Ctrl-D line to fix it. After removing the additional Volumegroup, everything get's ok. I found this out by replacing the raid5 device with some raid1 devices. That resulted in: 2.6.5smp-358 finds the additional Volumegroup and messes up during the boot process like 2.6.6-435 Regards Heiko Jakob This bug could be a duplicate of Bug #120292. I'm not sure, but there's also a problem about LVM2 and badblocks at startup with newer kernel versions. What i don't know is, has this guy more than 1 volume group. There've been lots of changes: have recent versions fixed this? Assuming fixed by 2.00.29. Reopen if not. |