Bug 1007406
Summary: | LVM on Raid 1 array gets stuck in read only after reboot when lvmetad+lvm autoactivation is used | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Peter Rajnoha <prajnoha> |
Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | agk, alanjgagne, arempter, bmarzins, bmr, cmarthal, dwysocha, gmazyland, heinzm, jbrassow, jonathan, liling, lvm-team, msnitzer, nperic, prajnoha, prockai, thornber, zkabelac |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.100-3.el6 | Doc Type: | Bug Fix |
Doc Text: |
When using MD RAID devices as PVs on top of which LVM logical volumes are defined and while lvmetad is enabled at the same time (global/use_lvmetad=1 lvm.conf setting), the accompanying logical volume autoactivation that is used together with lvmetad could cause dangling incomplete device-mapper devices representing logical volumes to be left in the system. This also kept the system in inconsistent state where the logical volumes could not be activated any further without manual cleanup of the dangling device-mapper devices. This was caused by triggering the LVM autoactivation at improper time during MD RAID array setup or deactivation. When the MD RAID array is not yet set up completely or it is being deactivated, the autoactivation of LVM logical volumes on top of it fails. This has been fixed and the LVM logical volume is autoactivated at proper time only when the MD RAID device is ready for use.
|
Story Points: | --- |
Clone Of: | 985638 | Environment: | |
Last Closed: | 2013-11-21 23:28:17 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: | 985638 | ||
Bug Blocks: |
Description
Peter Rajnoha
2013-09-12 12:29:59 UTC
The bug #1002144 is also an incarnation of this bug - incorrect MD handling while trying to scan the PVs to update lvmetad and running autoactivation at improper time. Could not reproduce this problem with lvm2-2.02.100-5.el6.x86_64 Both with a running system and commands as stated above, and with a reboot. Everything worked, no read-only occurences (with use_lvmetad=1 and lvm2-lvmetad on). Marking this concrete case as VERIFIED. 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. http://rhn.redhat.com/errata/RHBA-2013-1704.html |