13.07.2015 Views

[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

usFileSystemRevision: A 16-bit, binary-coded decimal number that indicates the revision of thefile system, if any. The first two (most significant) digits (8-bits) indicate the major revisionwhile the last two (least significant) digits (8-bits) indicate the minor revision (for example,0x0250 represents revision 2.50).ulDesiredUnitAllocationSize: The size, in bytes, of the allocation unit for the file system. Thevalue MUST be a power of 2. If the value is 0, a default allocation unit determined by the filesystem type is used. The allocation unit range is file system-dependent.pwszLabel: The null-terminated Unicode string to assign to the new file system. The maximumlabel size is file system-dependent.bForce: A Boolean that determines whether a file system format is forced, even if the partition isin use.bQuickFormat: A Boolean that determines whether a file system is quick formatted. A quickformat does not verify each sector on the volume.bEnableCompression: A Boolean that determines whether a file system is created withcompression enabled.ppAsync: A pointer to an IVdsAsync interface that, if the operation is successfully completed,receives the IVdsAsync interface to monitor and control this operation. Callers MUST releasethe interface when they are done with it.Return Values: The method MUST return zero or a non-error HRESULT (as specified in [<strong>MS</strong>-ERREF]) to indicate success, or return an implementation-specific nonzero error code toindicate failure. For the HRESULT values predefined by the <strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> Remote<strong>Protocol</strong>, see section 2.2.3.Note This method is not valid on CD/DVD or super floppy devices. These devices do notsupport partition table.ERROR_SUCCESS (0x00000000)When the server receives this message, it MUST validate the following parameter:•Verify that ppAsync is not NULL.•Verify that the partition at offset ullOffset is an OEM, ESP, recovery, or unknown partition.•Create a new async object implementing the IVdsAsync interface with an output type of<strong>VDS</strong>_ASYNCOUT_FORMAT and set the pointer ppAsync references to the interface.•Return an HRESULT indicating failure or success. Any errors encountered up through this point inprocessing the FormatPartitionEx operation are returned in this HRESULT.The server MUST perform the following. Errors generated in this sequence of steps are returned inthe pHrResult parameter to the IVdsAsync::Wait or IVdsAsyncQueryStatus methods.•If the operating system is unable to format the device using the file system type that is specifiedusing the type parameter, then this method MUST return <strong>VDS</strong>_E_INCOMPATIBLE_FILE_SYSTEM.•If the target device\media is write-protected, then this method MUST return<strong>VDS</strong>_E_MEDIA_WRITE_PROTECTED.[<strong>MS</strong>-<strong>VDS</strong>] — v20110610<strong>Virtual</strong> <strong>Disk</strong> <strong>Service</strong> (<strong>VDS</strong>) <strong>Protocol</strong> <strong>Specification</strong>Copyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011230 / 360

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!