info: Read MDADM arrays as their size, not the size of their underlying driveswip/info-udisks2-mdadm

These are exposed to the user as the size of the array. If we find such
an array, read its size, record the drives and don't count their sizes
individually.

This is slightly fiddly for a couple of reasons:

  - There's no API exposed in udisks2 to get directly from the
    UDisksMDRaid object to the underlying UDisksDrives, so we have to
    construct proxies manually.
  - We might see the drives first, before we encounter the RAID array.
    So we keep a reference to the UDisks objects when counting disk
    sizes and then use this to later on subtract the size if we later
    find out a drive is actually part of an array.

0 files changed, 0 insertions, 0 deletions