The motivation here is to enable hardware vendors to use regular md arrays for fwraid without the need for mdmonitor. The difficulty is that there will be nothing to distinguish these fwraid arrays from any other user-created array whose members are disks.
Existing arrays whose members/parents are all partitionable will be partitionable. Existing arrays whose members/parents are all disks will be treated as disks.
It shouldn't be possible to delete such arrays in anaconda. They should be treated like fwraid arrays. It will be possible to delete them in blivet by scheduling an `ActionDestroyFormat`/`ActionDestroyDevice` action pair, but calling `DeviceTree.recursiveRemove` on them will not destroy the array.
When is it wrong to update the origFormat from the format when building a device tree? In other words, why do you need that parameter at all?
It is possible to call `DeviceTree.populate` at any point, including after scheduling a reformat. It is important that originalFormat actually be the original format and not just the format it had when `addUdevDevice` ran last. The most obvious example of this is with network-attached block devices that get added one at a time from anaconda.
Closed.
anaconda-patches@lists.fedorahosted.org