Skip to content

Latest commit

 

History

History
157 lines (95 loc) · 6.34 KB

ns-vds-vds_volume_prop2.md

File metadata and controls

157 lines (95 loc) · 6.34 KB
UID title description helpviewer_keywords old-location tech.root ms.assetid ms.date ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames req.redist ms.custom f1_keywords dev_langs topic_type api_type api_location api_name
NS:vds._VDS_VOLUME_PROP2
VDS_VOLUME_PROP2 (vds.h)
Defines the properties of a volume object. This structure is identical to the VDS_VOLUME_PROP structure, except that it also includes the volume GUIDs.
*PVDS_VOLUME_PROP2
PVDS_VOLUME_PROP2
PVDS_VOLUME_PROP2 structure pointer
VDS_VOLUME_PROP2
VDS_VOLUME_PROP2 structure
base.vds_volume_prop2
vds/PVDS_VOLUME_PROP2
vds/VDS_VOLUME_PROP2
base\vds_volume_prop2.htm
base
e99aaead-f5ad-4181-9208-9158e9fac38f
12/05/2018
*PVDS_VOLUME_PROP2, PVDS_VOLUME_PROP2, PVDS_VOLUME_PROP2 structure pointer, VDS_VOLUME_PROP2, VDS_VOLUME_PROP2 structure, base.vds_volume_prop2, vds/PVDS_VOLUME_PROP2, vds/VDS_VOLUME_PROP2
vds.h
Windows
Windows 7 [desktop apps only]
Windows Server 2008 R2 [desktop apps only]
Windows
VDS_VOLUME_PROP2, *PVDS_VOLUME_PROP2
19H1
_VDS_VOLUME_PROP2
vds/_VDS_VOLUME_PROP2
PVDS_VOLUME_PROP2
vds/PVDS_VOLUME_PROP2
VDS_VOLUME_PROP2
vds/VDS_VOLUME_PROP2
c++
APIRef
kbSyntax
HeaderDef
Vds.h
VDS_VOLUME_PROP2

VDS_VOLUME_PROP2 structure

-description

[Beginning with Windows 8 and Windows Server 2012, the Virtual Disk Service COM interface is superseded by the Windows Storage Management API.]

Defines the properties of a volume object. This structure is identical to the VDS_VOLUME_PROP structure, except that it also includes the volume GUIDs.

-struct-fields

-field id

The GUID of the volume.

-field type

A VDS_VOLUME_TYPE enumeration value that specifies the volume type. Volume types are simple, spanned, striped (RAID-0), mirrored, or striped with parity (RAID-5).

-field status

A VDS_VOLUME_STATUS enumeration value that specifies the status of the volume.

-field health

A VDS_HEALTH enumeration value that specifies the health state of the volume.

-field TransitionState

A VDS_TRANSITION_STATE enumeration value that specifies the transition state of the volume.

-field ullSize

The size of the volume, in bytes.

-field ulFlags

A bitmask of VDS_VOLUME_FLAG enumeration values that describe the volume.

-field RecommendedFileSystemType

A VDS_FILE_SYSTEM_TYPE enumeration value that specifies the preferred file system for the volume. Must be one of the following: VDS_FST_NTFS, VDS_FST_FAT, VDS_FST_FAT32, VDS_FST_UDF, VDS_FST_CDFS, or VDS_FST_UNKNOWN.

-field cbUniqueId

The length of the byte array that the pUniqueId member points to.

-field pwszName

The name that was used to open a handle for the volume with the CreateFile function. For example, \?\GLOBALROOT\Device\HarddiskVolume1.

-field pUniqueId

A byte array that contains the unique identifier for the volume.

-remarks

The IVdsVolume2::GetProperties2 method returns this structure to report the properties of a volume object.

When a volume is offline, the VDS_VF_PERMANENTLY_DISMOUNTED flag is set in the ulFlags member of the VDS_VOLUME_PROP2 structure, and the VDS_VS_OFFLINE volume status value is also set in the status member of this structure.

For GPT and dynamic volumes, the unique identifier that the pUniqueId member points to is globally unique.

For removable media drives, the volume exists and has its own unique identifier even if there is no media in the device. If a volume is formatted on removable media, that volume has its own unique identifier. For more information, see Supporting Mount Manager Requests in a Storage Class Driver.

The format of the unique identifier may vary among different types of devices and volumes. For basic volumes on MBR disks, the unique identifier is based on the disk signature and partition offset. Because the disk signature and partition offset are DWORD values, the unique identifier cannot be guaranteed to be globally unique across computers.

If the disk signature changes, the volume's unique identifier also changes. Disk signature changes usually occur as a result of a collision during disk cloning.

Note that a unique identifier is not the same as a volume GUID path. To find the volume GUID paths for a volume, use the IVdsVolumeMF3::QueryVolumeGuidPathnames method.

-see-also

IVdsVolume2::GetProperties2

MOUNTDEV_UNIQUE_ID

VDS Structures

VDS_FILE_SYSTEM_TYPE

VDS_HEALTH

VDS_TRANSITION_STATE

VDS_VOLUME_FLAG

VDS_VOLUME_STATUS

VDS_VOLUME_TYPE