Bug 427377 - HA LVM should allow multiple LVs/VG as long as they move together
HA LVM should allow multiple LVs/VG as long as they move together
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: rgmanager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jonathan Earl Brassow
Cluster QE
Depends On:
Blocks: 427378
  Show dependency treegraph
Reported: 2008-01-03 11:42 EST by Jonathan Earl Brassow
Modified: 2010-10-22 17:29 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2008-0791
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-25 15:15:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Earl Brassow 2008-01-03 11:42:45 EST
The restriction that there can be only one LV per VG in HA LVM can be
cumbersome.  It was done that way to ensure different machines did not alter the
same metadata if LVs were in use in different places.

We can releave some of the pain by allowing multiple LVs per VG if, and only if,
they move together.  IOW, all services which rely on a particular volume group
must exist on only one machine at a time.
Comment 1 RHEL Product and Program Management 2008-01-03 11:45:24 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 3 Debbie Johnson 2008-03-14 09:13:42 EDT
another customer has reported this issue and it appears already has been given
the patch .. The testing was successful.  I have attached the IT to this BZ.

Let me know if there is anything else I can do.
Comment 7 errata-xmlrpc 2008-07-25 15:15:46 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.