Attempting to use mdadm-1.2.0 on a 1.5 TB device yields: ------------ # fdisk /dev/sda Command (m for help): p Disk /dev/sda: 1498.9 GB, 1498918420480 bytes 255 heads, 63 sectors/track, 182233 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 125 1004031 fd Linux raid autodetect /dev/sda2 126 182233 1462782510 fd Linux raid autodetect Command (m for help): q # mdadm --create /dev/md1 -c 64 -l multipath -n 2 /dev/sda2 /dev/sdc2 mdadm: /dev/sda2 is too small: -684701138K mdadm: /dev/sdc2 is too small: -684701138K mdadm: create aborted ------------ This appears to be the result of mdadm's use of signed 32-bit integers relating to capacity variables. mdadm-1.6.0 does not suffer from this issue. What is keeping it out of KEYWORDS="x86"?
Is this really a bug then? If it is resolved in a newer version that's already in portage, feel free to use it.
1.6.0 moved to stable
*** Bug 61205 has been marked as a duplicate of this bug. ***
Moving to Release Media/Installer.