Using a newer mdadm version just for re-adding a device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello.

Is it safe to mix mdadm versions in the following scenario?

openSUSE 12.1 comes with mdadm 3.2.2 (and kernel 3.1), which works fine
except that I am hit by the re-add bug:
I removed a partition (after "mdadm --manage --set-faulty ...") from a perfectly
working /dev/md1, but re-adding with "mdadm /dev/md1 -a ..." fails.
Reading the mailing list and the Changelog, I understand that
this is fixed in mdadm 3.2.5.
Hence, I compiled mdadm 3.2.5 from source.

Now my question is:
Can I safely use the resulting binary (renamed to mdadm325 to avoid confusion)
to re-add the device and then continue to use the 3.2.2 package from openSUSE?

Thanks for reading
Sven
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux