This is a regression in Hardy which is very simple to fix and otherwise
prevents the use of fakeraid disks (limited hardware controllers on
motherboards) with RAID level 4 and 5.
Fix description: Device-mapper targets normally follow a certain naming
scheme, which enables loading missing target types. The fix will change
the Makefile in LUM to build dm-raid45.ko instead of dm-raid4-5.ko.
Patch: attached
Testcase: Activation of dmraid for RAID4 or RAID5 arrays fails with
error message "dm-raid45 is not in kernel". Verification of fix has been
documentet in the bug report.
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
05-05-2008, 06:15 PM
Tim Gardner
SRU request for LP Bug#220493
Stefan Bader wrote:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/220493
>
> SRU Justification:
>
> Impact: Regression for users of dmraid.
>
> This is a regression in Hardy which is very simple to fix and otherwise
> prevents the use of fakeraid disks (limited hardware controllers on
> motherboards) with RAID level 4 and 5.
>
> Fix description: Device-mapper targets normally follow a certain naming
> scheme, which enables loading missing target types. The fix will change
> the Makefile in LUM to build dm-raid45.ko instead of dm-raid4-5.ko.
>
> Patch: attached
>
> Testcase: Activation of dmraid for RAID4 or RAID5 arrays fails with
> error message "dm-raid45 is not in kernel". Verification of fix has been
> documentet in the bug report.
>
ACK - though I imagine folks that have already worked around this bug
will be annoyed.
--
Tim Gardner tim.gardner@ubuntu.com
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
SRU request for LP Bug#220493
