HostVmfsSpec
This data object type describes the VMware File System (VMFS) creation specification.
Once created, these properties for the most part cannot be changed. There are a few exceptions.
{
"_typeName": "string",
"extent": {
"_typeName": "string",
"diskName": "string",
"partition": 0
},
"blockSizeMb": 0,
"majorVersion": 0,
"volumeName": "string",
"blockSize": 0,
"unmapGranularity": 0,
"unmapPriority": "string",
"unmapBandwidthSpec": {
"_typeName": "string",
"policy": "string",
"fixedValue": 0,
"dynamicMin": 0,
"dynamicMax": 0
}
}
This data object type describes the specification of a Disk partition.
Deprecated as of vSphere API 6.5, use blockSize instead.
The block size of VMFS in megabytes (MB).
Determines the maximum file size. If this optional property is not set, the maximum file size defaults to the maximum file size for the platform.
In VMFS2, the valid block sizes 1MB, 2MB, 4MB, 8MB, 16MB, 32MB, 64MB, 128MB, and 256MB. In VMFS3, the valid block sizes are 1MB, 2MB, 4MB, and 8MB. In VMFS5, the only valid block size is 1MB.
Major version number of VMFS.
This can be changed if the VMFS is upgraded, but this is an irreversible change.
Volume name of VMFS.
The block size of VMFS in kilotypes (KB).
Determines the maximum file size. If this optional property is not set, the maximum file size defaults to the maximum file size for the platform.
In VMFS3, the valid block sizes are 1MB, 2MB, 4MB, and 8MB. In VMFS5, the only valid block size is 1MB. In VMFS6, the valid block sizes are 64KB and 1MB.
The granularity of VMFS unmap operations.
VMFS unmap reclaims unused storage space. The unit is KB. The minimum unmap granularity is 8KB. The maximum unmap granularity is determined by the block size of VMFS blockSize.
VMFS unmap priority.
VMFS unmap reclaims unused storage space. This determines the processing rate of unmaps. See HostVmfsVolumeUnmapPriorityEnum for supported values.
VMFS unmap reclaims unused storage space.
This data object type describes the specification of VMFS unmap bandwidth.