Device\CIM_CompositeExtentBasedOn.mof.mof (HTML version)

Return to index
CIM_CompositeExtentBasedOn Superclass: CIM_BasedOn
This specialization defines how data is striped across StorageExtents. Additionally, it includes information on distribution of check data so that the 'usual case' RAID devices can be created in one step.
Qualifiers:Version ( "2.7.0" ) UMLPackagePath ( "CIM::Device::StorageExtents" ) Association
Parameters (local in grey)
boolean LBAMappingIncludesCheckData ;
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.
Required
MappingStrings { "MIF.DMTF|Protected Space Extent|001.1" }
Override ( "OrderIndex" )
uint16 OrderIndex ;
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.
Punit ( "byte" )
MappingStrings { "MIF.DMTF|Protected Space Extent|001.6" }
Units ( "Bytes" )
uint64 UserDataStripeDepth ;
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.
Punit ( "byte" )
MappingStrings { "MIF.DMTF|Physical Extent|001.8" }
Units ( "Bytes" )
uint64 UnitsOfUserData ;
Number of bytes to be reserved for user data.
Punit ( "byte" )
MappingStrings { "MIF.DMTF|Physical Extent|001.7" }
Units ( "Bytes" )
uint64 UnitsOfCheckData ;
Number of bytes to be reserved for check data.
Punit ( "byte" )
MappingStrings { "MIF.DMTF|Physical Extent|001.6" }
Units ( "Bytes" )
uint64 UnitsBeforeCheckDataInterleave ;
Number of bytes of user data to skip before starting the check data interleave.
Override ( "Dependent" )
CIM_CompositeExtent REF Dependent ;
The CompositeExtent which is built on the StorageExtent.
MappingStrings { "MIF.DMTF|Protected Space Extent|001.3" }
ModelCorrespondence { "CIM_StorageExtent.NumberOfBlocks" }
uint64 NumberOfBlocks ;
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.
Punit ( "byte" )
MappingStrings { "MIF.DMTF|Protected Space Extent|001.4" }
Units ( "Bytes" )
ModelCorrespondence { "CIM_StorageExtent.BlockSize" }
uint64 BlockSize ;
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.
boolean LBAsMappedByDecrementing ;
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.
Min ( 1 )
Override ( "Antecedent" )
CIM_StorageExtent REF Antecedent ;
The underlying StorageExtent.
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.