Red Hat Bugzilla – Bug 739162
RFE: LVM RAID - Support snapshot of RAID
Last modified: 2012-08-27 10:54:00 EDT
Make it possible to take a snapshot of RAID targets (RAID 1/4/5/6).
Release criteria (test requirements):
Ensure that snapshots can be taken of each of the different RAID types (raid1, raid4, raid5, raid5_ls, raid5_la, raid5_rs, raid5_ra, raid6, raid6_zr, raid6_nr, raid6_nc) - that they can be created and remove. In short, the same snapshot testing should be performed on RAID that is performed on linear or other devices.
All userspace code is in place for snapshots as of the 2.02.89 release. The kernel has a know issue however. That is filed under bug 785182 and is blocking this bug.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Feature to 6.3. No documentation required.
Bug 732458 is the bug that requires a release note for the RAID features. Other documentation is found in the LVM manual.
Operational bugs need no documentation because they are being fixed before their initial release.
Basic snapshot regression tests have now passed on raid origin volumes with the latest kernel/lvm rpms. Marking verified.
lvm2-2.02.95-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
lvm2-libs-2.02.95-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
lvm2-cluster-2.02.95-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
udev-147-2.41.el6 BUILT: Thu Mar 1 13:01:08 CST 2012
device-mapper-1.02.74-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
device-mapper-libs-1.02.74-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
device-mapper-event-1.02.74-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
device-mapper-event-libs-1.02.74-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
cmirror-2.02.95-10.el6 BUILT: Fri May 18 03:26:00 CDT 2012
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.