Red Hat Bugzilla – Bug 480733
2 volume rebuilding problem - second volume rebuild doesn't succeed.
Last modified: 2009-09-02 04:59:28 EDT
When creating 2 RAID VOLUME, rebuilding on the second volume doesn't succeed.
During rebuild I got info on screen: "device-mapper: dm-raid45: io_put would go negative!!!"
When doing the same on the first volume, rebuild succeeds.
Steps to reproduce.
dmraid -f isw -C r5d3n1s64-5 --type 5 --strip 64K --size 5G --disk "/dev/sdb /dev/sdc /dev/sdd"
dmraid -f isw -C r5d3n0s64-5 --type 5 --strip 64K --size 5G --disk "/dev/sdb /dev/sdc /dev/sdd"
dmraid -a y
mount /dev/mapper/isw_cgdihgcccd_r5d3n0s64-5 /mnt/isw_cgdihgcccd_r5d3n0s64-5
openssl rand -out /mnt/isw_cgdihgcccd_r5d3n0s64-5/testfile.bin 536870912
dmraid -f isw -S -M /dev/sde
!!!REMOVE DRIVE HERE!!!
dmraid -R isw_cgdihgcccd_r5d3n0s64-5
!!!NOTHING HAPPENS HERE!!!
Expected results when rebuilding is finished:
isw_cgdihfhgac_r5d3n0s64-5: 0 632840448 raid45 3 8:48 8:16 8:32 1 AAA
TestPC6_1231936876058# Rebuild status for isw_cgdihfhgac_r5d3n0s64-5 is AAA
Actual results when rebuilding is finished:
isw_cgdihfhgac_r5d3n0s64-5: 0 632840448 raid45 3 8:48 8:16 8:32 1 AiAA
TestPC6_1231936876058# Rebuild status for isw_cgdihfhgac_r5d3n0s64-5 is AiAA
-Device mapper: 1.02.28 (2008-09-18)
Issue does not reproduce.
We got rebuild error because design of the test was wrong.
This bug should be closed.
Reopening, because I don't think that any test design may be allowed to trigger that target internal error "device-mapper: dm-raid45: io_put would go negative!!!".
This has to be regression tested, because my new kernel patch corrects this io reference counting (io_get/io_put) pairs.
Patch committed to rhkernel-list for RHEL5.4 inclusion.
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
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 therefore 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.