On 07/18/2012 11:08 AM, Danny Wood wrote:Hi Mark-Willem Jansen Seconded WRT the niche market. It's usually only used by the people who run a dual boot with Windows as Mdadm is far superior for pure Linux installs. The later is exactly why things move to MD and eg. we're doing a device-mapper target wrapper to access the MD kernel runtime in order to make it accessible in LVM. Because the MD runtime has the long established field record it has, major FAKERAID OEMs decided to use it (namly Intel with their Intel Matrix RAID, isw in dmraid). mdadm gained external metadata format support along the lines of dmraid to allow for that and thus supports isw for long time now. As a result of that, Red Hat decided to not further develop dmraid. Actually we already asked publically, if dmraid is still mandatory to support the other metadata formats than DDF, Intel Matrix RAID and MD, which are supported by mdadm now anyway. No arguments it's still needed resulted from that so far.
There's no need to have code duplication for partitioinig support in another tool. For the record: the DOS partitioning support got added way back in time before kpartx addressed it (and never got pulled out). So use kpartx for activating partitionins on RAID sets. The most important question (as mentioned above) still persists though: is dmraid still needed or is any further development adequate to support the Adaptec, Highpoint, Jmicron, LSI, NVidia, Promise, Silicon Image and VIA metadata formats? Are they still being used that much in the field or are users just happy with dmraid access to those in their mixed Linux/Windows environments? Requirement for pure Linux environment is MD/LVM anyway. We better get field feedback which we didn't get so far to answer that question. Heinz
|
_______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
