DiskPartitions should be BasedOn a single StorageVolume (for example, exposed by a hardware RAID cabinet), an SCC VolumeSet, or realized directly in PhysicalMedia. The first two relationships are made explicit in this association. The latter is conveyed by the RealizesDiskPartition association. | Qualifiers:Version ( "2.8.1000" ) Association | Parameters (local in grey) | | Override ( "Dependent" ) CIM_GenericDiskPartition REF Dependent ; The DiskPartition which is built on the Volume. | Max ( 1 ) Override ( "Antecedent" ) CIM_StorageVolume REF Antecedent ; The StorageVolume. | uint64 EndingAddress ; EndingAddress indicates where in lower level storage, the higher level Extent ends. This property is useful when mapping non-contiguous Extents into a higher level grouping. | uint64 StartingAddress ; StartingAddress indicates where in lower level storage, the higher level Extent begins. | uint16 OrderIndex ; If there is an order to the BasedOn associations that describe how a higher level StorageExtent is assembled, the OrderIndex property indicates this. When an order exists, the instances of BasedOn with the same Dependent value (i.e., the same higher level Extent) should place unique values in the OrderIndex property. The lowest value implies the first member of the collection of lower level Extents, and increasing values imply successive members of the collection. If there is no ordered relationship, a value of zero should be specified. An example of the use of this property is to define a RAID-0 striped array of 3 disks. The resultant RAID array is a StorageExtent that is dependent on (BasedOn) the StorageExtents that describe each of the 3 disks. The OrderIndex of each BasedOn association from the disk Extents to the RAID array could be specified as 1, 2 and 3 to indicate the order in which the disk Extents are used to access the RAID data. |
| | | | |
|