Bug 164198
Summary: | LV activation issues when attempting large numbers | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 4.0 | CC: | agk, jbrassow |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-08-08 19:01:32 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
Corey Marthaler
2005-07-25 21:15:51 UTC
A little more detail: LVM2 was used in its cluster capacity to create 1500 lvs on a VG that was not active. After doing a 'vgchange -ay', only 432 LVs were available. 'lvchange -ay' was tried - still 432 LVs. Trying to activate an individual LV (lvchange -ay /dev/gfs/gfs1066) not only failed to activate it, but reported success. clvmd was shutdown, and the locking_type was switched back to single machine. This is when the lvm process grew out of control. Reassign to agk as this doesn't seem to be cluster-related. See also bug 164197: I suspect the '432' limit may be related. Yes, fixing bug 164197 will get you past your '432' limit. *** This bug has been marked as a duplicate of 164197 *** |