HostUnresolvedVmfsResolutionResult
When an UnresolvedVmfsVolume has been resignatured or forceMounted, we want to return the original spec information along with newly created VMFS volume.
{
"_typeName": "string",
"spec": {
"_typeName": "string",
"extentDevicePath": [
"string"
],
"uuidResolution": "string"
},
"vmfs": {
"_typeName": "string",
"type": "string",
"name": "string",
"capacity": 0,
"blockSizeMb": 0,
"blockSize": 0,
"unmapGranularity": 0,
"unmapPriority": "string",
"unmapBandwidthSpec": {
"_typeName": "string",
"policy": "string",
"fixedValue": 0,
"dynamicMin": 0,
"dynamicMax": 0
},
"maxBlocks": 0,
"majorVersion": 0,
"version": "string",
"uuid": "string",
"extent": [
{
"_typeName": "string",
"diskName": "string",
"partition": 0
}
],
"vmfsUpgradable": false,
"forceMountedInfo": {
"_typeName": "string",
"persist": false,
"mounted": false
},
"ssd": false,
"local": false,
"scsiDiskType": "string"
},
"fault": {
"_typeName": "string",
"faultCause": "MethodFault Object",
"faultMessage": [
{
"_typeName": "string",
"key": "string",
"arg": [
{
"_typeName": "string",
"key": "string",
"value": {
"_typeName": "string"
}
}
],
"message": "string"
}
]
}
}
An unresolved VMFS volume is reported when one or more device partitions of volume are detected to have copies of extents of the volume.
Such copies can be created via replication or snapshots, for example. This data object type describes how to resolve an unbound VMFS volume. The SCSI device path for each of the VMFS volume extent should be specified. For the current release, only head-extent needs to be specified. In future releases, we will allow user to specify explicitly all the extents which makes up a new Vmfs Volume.
The base data object type for all the object model faults that an application might handle.