-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/19/2012 03:30 PM, Mark-Willem Jansen wrote: > I do not know the finer detail of mdadm, yet. But I saw > super-mbr.c and super-gpt.c and and draw the conclusion, taken how > dmraid handles mbr, that these were codes to parse mbt and gpt > partition tables. Ah, gotcha - I think this code was introduced a few years after the external metadata support was added (not sure though, would have to look in git) and is handled in the same manner as the DDF, Intel and native MD metadata formats. Unlike those formats though you cannot assemble arrays from MBR or gpt metadata - they're only used when adding new bare devices to arrays so that the member partitions can be used. >> I think adding new format handlers to MD is a much better idea; >> the dominant formats backed by major OEMs are already using it >> so if there's interest in the less commonly used formats I think >> they would see much better maintenance and continued development >> in an active project like mdadm than they would in a revived >> dmraid. > > So it would be time that someone(probably me) starts adding the > Promise formats used by the AMD chip-sets. Cool! Seems like a good direction. I'd be interested in having a look at this too. Regards, Bryn. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAILqoACgkQ6YSQoMYUY967mgCg1R+u1ROnHe1gEmD56gPVA4Ot 3f8AoKtc7IKv6Sct5RIj16ovqa+rqpO5 =qyIZ -----END PGP SIGNATURE----- _______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
