association CIM_CompositeExtentBasedOn : CIM_BasedOn

Description:

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.

Definition:

Feature Type Class Origin Qualifiers
Antecedent CIM_StorageExtent CIM_Dependency
Override Antecedent
Min 1
Description The underlying StorageExtent.
Key TRUE
Dependent CIM_StorageExtent CIM_Dependency
Override Dependent
Description The StorageExtent which is built on the StorageExtent.
Key TRUE
StartingAddress uint64 CIM_BasedOn
Description StartingAddress indicates where in lower level storage, the higher level Extent begins.
EndingAddress uint64 CIM_BasedOn
Description 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.
OrderIndex uint16 CIM_BasedOn
Required TRUE
Override OrderIndex
Description Order matters to composite extents. 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 composite extent 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.
MappingStrings MIF.DMTF|Protected Space Extent|001.1
LBAsMappedByDecrementing boolean CIM_CompositeExtentBasedOn
Description True if logical blocks in the underlying StorageExtents are mapped in decrementing order. This property corresponds to the INCDEC value in the SCSI SCC-2 Volume Set PS_Extent Descriptor.
LBAMappingIncludesCheckData boolean CIM_CompositeExtentBasedOn
Description 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.
NumberOfBlocks uint64 CIM_CompositeExtentBasedOn
Description 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 SCSI SCC, this is equivalent to the NUMBER OF LBA_PS(s) field in the Volume Set PS_Extent Descriptor.
MappingStrings MIF.DMTF|Protected Space Extent|001.3
ModelCorrespondence CIM_StorageExtent.NumberOfBlocks
BlockSize uint64 CIM_CompositeExtentBasedOn
Description The Dependent's BlockSize is limited by the Antecedent's. In SCSI SCC, this is equivalent to the NUMBER OF BYTES PER LBA_PS field in the RedundancyGroup P_Extent Descriptor.
Units Bytes
MappingStrings MIF.DMTF|Protected Space Extent|001.4
ModelCorrespondence CIM_StorageExtent.BlockSize
PUnit byte
UserDataStripeDepth uint64 CIM_CompositeExtentBasedOn
Description 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.
Units Bytes
MappingStrings MIF.DMTF|Protected Space Extent|001.6
PUnit byte
UnitsBeforeCheckDataInterleave uint64 CIM_CompositeExtentBasedOn
Description Number of bytes of user data to skip before starting the check data interleave.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.6
PUnit byte
UnitsOfCheckData uint64 CIM_CompositeExtentBasedOn
Description Number of bytes to be reserved for check data.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.7
PUnit byte
UnitsOfUserData uint64 CIM_CompositeExtentBasedOn
Description Number of bytes to be reserved for user data.
Units Bytes
MappingStrings MIF.DMTF|Physical Extent|001.8
PUnit byte

Typographical Conventions:

  1. Inherited properties are italicized.
  2. Local properties are bolded.
  3. Key properties are highlighted in gold

Generated by mof2html v.2.1.0(002). simplewbem.org Mon Nov 2 09:43:14 2009