Red Hat Bugzilla – Bug 499246
vol_id mis-prioritizes dmraid vis a vis mdraid
Last modified: 2009-07-22 17:44:20 EDT
Created attachment 342523 [details]
Switch the priority.
Description of problem: vol_id shows linux_raid_member sometimes when isw_raid_member would be more appropriate.
Version-Release number of selected component (if applicable):
How reproducible: Always.
Steps to Reproduce:
1. Create a two dmraid raid-1 devices
2. Use one of them in an md raid
run vol_id --probe-all on the raw (sd*) devices. On disks in the dmraid device that's not part of the md raid, it'll show "isw_raid_member" (assuming isw is our dmraid format). On disks that are part of the dmraid device that is used in the md raid, it'll show "linux_raid_member" and then "isw_raid_member".
On the devices that are part of the dmraid device used in the md raid device, they should have the opposite priority.
Additional info: Patch attached.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
udev-141-4.fc11 has been submitted as an update for Fedora 11.
udev-141-4.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update udev'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7208
udev-141-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.