Hi all,
A while ago the following was posted, nd I am experiencing the same - the HW provider is not detecting the other hidden volumes even though they are surfaced on the system. I can go in to diskpart and show volume details and see that they are hidden etc… but the HW provider does not recognise them when performing
CVssHardwareProviderWrapper::GetHiddenVolumeList:
Original post reposted below.
Many thanks for any help!
Hello,
I am developing a Hardware Provider for Windows 2003 server. The snapshot gets created successfully, but FillInLunInfo gets called infinitely. VSS keeps calling FillInLunInfo by passing the LUN, which happens to be the local hard disk of that server machine.
I switched on tracing feature of VSS(from the registry) to track what is actually the problem and observed the following, which might be the reason. But, I am not sure about the causes of the problem and wished to reconfirm. Thanks for the same. 1. When the shadow copy on a particular drive is taken, its shadow copy is discovered as a new physical drive by the windows system. It has log saying,
detected a new Drive :\.\PHYSICALDRIVE2.
But, after VssHardwareProvider::Wrapper::GetHiddenVolumeList function of VSS detects only 3 hidden volumes(2 are Windows server’s local disks volumes and the other one is original volume on which the snapshot was taken). It does not detect the hidden volume on the shadow disk. This is the behavior of my provider.
I compared it against the logs of sample provider from Microsoft, it detects 4 hidden volumes - 2 volumes of the server’s local disks, 1 is the original volume and the one is the shadow volume.
The VSS Service calls BuildLunInfoFromVolume for all the volumes that are detected and FillInLunInfo gets called that many times for each LUN. Once a matching LUN is found the post shadow copy creation completes.
I think this is one of the reasons why FillInLunInfo goes in an infinite loop. FillInLunInfo fails to find a matching LUN as the volume present on shadow copy disk is not detected.
Could you please tell me whether the windows hardware provider has to make some special call to make the volumes on the shadow copy LUN visible may be from LocateLuns, or is it the target end’s problem(i.e. data corruption) or something.
Thanks and Regards,
Priya