Key |
Antecedent
|
CIM_ManagedElement
|
|
Antecedent represents the independent object in this association. |
Dependent
|
CIM_ManagedElement
|
|
Dependent represents the object that is dependent on the Antecedent. |
Read Only |
BlockSize
|
uint64
|
|
The Dependent's BlockSize is limited by the Antecedent's. In SCC, this is equivalent to the NUMBER OF BYTES PER LBA_PS field in the RedundancyGroup P_Extent Descriptor. |
LBAMappingIncludesCheckData
|
boolean
|
|
True if the logical block mapping algorithm includes check data bytes. This property corresponds to the NOCHKSKIP attribute in the SCC-2 Volume Set PS_Extent Descriptor. |
LBAsMappedByDecrementing
|
boolean
|
|
True if logical blocks in the underlying StorageExtents are mapped in decrementing order. This property corresponds to the INCDEC value in the SCC-2 Volume Set PS_Extent Descriptor. |
NumberOfBlocks
|
uint64
|
|
The total number of blocks that will be consumed on the Dependent Extent. This is limited by the Antecedent's NumberOfBlocks, but is included explicitly to provide for the DMTF MIF mapping. In SCC, this is equivalent to the NUMBER OF LBA_PS(s) field in the Volume Set PS_Extent Descriptor. |
OrderIndex
|
uint16
|
|
Order matters to CompositeExtents. An example of the use of this property is when defining a RAID-0 striped array of 3 disks. The resultant RAID array is a CompositeExtent that is dependent on (as described by CompositeExtentBasedOn) the StorageExtents that represent each of the 3 disks. The OrderIndex of each CompositeExtentBasedOn 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. |
UnitsBeforeCheckDataInterleave
|
uint64
|
|
Number of bytes of user data to skip before starting the check data interleave. |
UnitsOfCheckData
|
uint64
|
|
Number of bytes to be reserved for check data. |
UnitsOfUserData
|
uint64
|
|
Number of bytes to be reserved for user data. |
UserDataStripeDepth
|
uint64
|
|
Number of bytes which form the stripe size for the Dependent StorageExtent. If the CompositeExtent is concatenated instead of striped, then UserDataStripeDepth should be set to zero. |
Read Write |