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

3.4.5.1.4 Removing Disk ObjectsThe server MUST maintain a list of detected disks. When the server discovers that a disk wasremoved, it MUST remove the corresponding disk object from the list of storage managementobjects. For each callback object that is registered in the list of callback objects, the server MUSTcall the callback object's IVdsAdviseSink::OnNotify (Opnum 3) method with aVDS_NOTIFICATION structure that has the following attributes:•objectType member is VDS_NTT_DISK.•disk member is a VDS_DISK_NOTIFICATION that has the following attributes:•ulEvent is VDS_NF_DISK_DEPART.•diskId is the VDS_OBJECT_ID of the disk object that was removed.If the disk being removed is a basic disk, the pack that the disk belongs to is also removed. In thiscase, the server MUST remove the corresponding pack object from the list of storage managementobjects. Then, for each callback object that is registered in the list of callback objects, the serverMUST call the callback object's IVdsAdviseSink::OnNotify (Opnum 3) method with aVDS_NOTIFICATION structure that has the following attributes:•objectType member is VDS_NTT_PACK.•pack member is a VDS_PACK_NOTIFICATION that has the following attributes:•ulEvent is VDS_NF_PACK_DEPART.•packId is the VDS_OBJECT_ID of the pack object that was removed.3.4.5.1.5 Adding Volume ObjectsThe server MUST maintain a list of detected volumes. When the server discovers a new volume(either during initialization or when a new volume arrives after initialization), it checks whether thevolume resides on a basic disk or on one or more dynamic disks.Basic Disk: If the volume is on a basic disk, the server MUST create a corresponding volume objectand MUST assign it a unique VDS_OBJECT_ID. The server MUST set the volume object's packpointer to the pack object that corresponds to the pack to which the disk on which the volume iscontained belongs. The server MUST add the volume object to the list of storage managementobjects.For each callback object that is registered in the list of callback objects, the server MUST call thecallback object's IVdsAdviseSink::OnNotify (Opnum 3) method with a VDS_NOTIFICATIONstructure that has the following attributes:•objectType member is VDS_NTT_VOLUME.•volume member is a VDS_VOLUME_NOTIFICATION that has the following attributes:•ulEvent is VDS_NF_VOLUME_ARRIVE.•volumeId is the VDS_OBJECT_ID of the volume object that was added.Dynamic Disk: If the volume is on dynamic disks, the server MUST create a corresponding volumeobject and MUST assign it a unique VDS_OBJECT_ID. The server MUST set the volume object's[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011164 / 360