Hide Forgot
There are two table arguments that can be given to a DM RAID target that control whether the array is forced to (re)synchronize or skip initialization: "sync" and "nosync". When "sync" is given, we set mddev->recovery_cp to 0 in order to cause the device to resynchronize. This is insufficient if there is a bitmap in use, because the array will simply look at the bitmap and see that there is no recovery necessary. This means that a user cannot use the 'sync' directive to cause the array to resync itself. This is a low priority bug because a user can simply clear the bitmap area by writing zeros to it before assembling the array - which is what LVM does.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Two ways to test: 1) Create a RAID LV ~> lvcreate --type raid1 -m 1 -L 1G -n lv vg 2) Wait for it to sync ('lvs' output should read 100% for Cpy%Sync) 3) Issue a resync `> lvchange --resync vg/lv 4) Ensure the array is properly resyncing ('lvs' will build to 100%) For a more thorough testing, use device-mapper to replace step 3 above: # Load a new table with the additional 'sync' argument [~]# dmsetup table vg-lv | sed s:'3 128':'4 128 sync': | dmsetup load vg-lv # Suspend and resume to replace the old table with the new [~]# dmsetup suspend vg-lv [~]# dmsetup resume vg-lv # Ensure LV is resyncing [~]# lvs vg LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv vg rwi-a-r-- 5.00g 0.00 [~]# lvs vg LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv vg rwi-a-r-- 5.00g 18.74 [~]# lvs vg LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv vg rwi-a-r-- 5.00g 37.47 [~]# lvs vg LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv vg rwi-a-r-- 5.00g 100.00
Patch(es)
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/RHSA-2013-1645.html
clearing my needinfo flag for this closed bug