Bug 822243
| Summary: | raid volumes should not be created on cluster VGs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Jonathan Earl Brassow <jbrassow> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.4 | CC: | agk, dwysocha, heinzm, jbrassow, msnitzer, nperic, prajnoha, prockai, thornber, zkabelac |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.98-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, it was possible to have RAID logical volumes in a clustered volume group. RAID logical volumes are not cluster capable and activating them in a cluster can cause corruption. Thus, the ability to create RAID logical volumes in a cluster has been disabled.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 08:09:57 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: | |||
|
Description
Corey Marthaler
2012-05-16 19:38:22 UTC
This can cause issues when attempting operations like image splitting on raid volumes on cluster VGs.
SCENARIO - [sequentially_split_off_all_raid1_pvs]
Skipping this test case since cluster raids are not supported
Create a raid1 with many legs and then sequentially split off each one of the PVs
taft-02: lvcreate --type raid1 -m 4 -n split_pvs_sequentially -L 300M split_image
Waiting until all mirror|raid volumes become fully syncd...
0/1 mirror(s) are fully synced: ( 24.77% )
0/1 mirror(s) are fully synced: ( 55.96% )
0/1 mirror(s) are fully synced: ( 88.21% )
1/1 mirror(s) are fully synced: ( 100.00% )
splitting off legs:
/dev/sde1
couldn't split image
Error locking on node taft-04: Failed to rename split_image-split_pvs_sequentially_rimage_4 (253:12) to split_image-split_pvs_sequentially_rimage_3
Error locking on node taft-01: Failed to rename split_image-split_pvs_sequentially_rimage_4 (253:12) to split_image-split_pvs_sequentially_rimage_3
Error locking on node taft-03: Failed to rename split_image-split_pvs_sequentially_rimage_4 (253:12) to split_image-split_pvs_sequentially_rimage_3
Error locking on node taft-02: Failed to rename split_image-split_pvs_sequentially_rimage_4 (253:12) to split_image-split_pvs_sequentially_rimage_3
Failed to resume split_image/split_pvs_sequentially after committing changes
Unit test (Do not allow RAID LVs to be created in a cluster VG): [root@hayes-02 lvm2]# vgs vg VG #PV #LV #SN Attr VSize VFree vg 8 0 0 wz--nc 5.07t 5.07t [root@hayes-02 lvm2]# lvcreate --type raid1 -L 100M -n lv vg Unable to create a raid1 logical volume in a cluster. commit 9efd3fb604ae34803bb2d4c94080c57d3efdba81
Author: Jonathan Brassow <jbrassow>
Date: Wed Oct 3 15:52:54 2012 -0500
RAID: Do not allow RAID LVs in a cluster volume group.
It would be possible to activate a RAID LV exclusively in a cluster
volume group, but for now we do not allow RAID LVs to exist in a
clustered volume group at all. This has two components:
1) Do not allow RAID LVs to be created in a clustered VG
2) Do not allow changing a VG from single-machine to clustered
if there are RAID LVs present.
no RAID LV could be created by using lvcreate command. Marking as verified Software versions: lvm2-2.02.98-2.el6.x86_64 lvm2-cluster-2.02.98-2.el6.x86_64 device-mapper-1.02.77-2.el6.x86_64 cmirror-2.02.98-2.el6.x86_64 kernel-devel-2.6.32-330.el6.x86_64 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-0501.html |