Changes between Version 1 and Version 2 of Ticket #17828, comment 3
- Timestamp:
- Apr 17, 2020 5:38:54 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17828, comment 3
v1 v2 1 1 I'd like to co-sign this ticket. I have a base .vmdk on a Passport drive, with a .vmdk in the Snapshots directory on the faster main drive shadowing it, where (nearly) all the changed blocks reside. However the machine only shows a Current State entry, no snapshot files. The Virt. Media Mgr. shows the parent-child relationship between the base vmdk and the vmdk on the main drive. 2 2 3 I would like to move the base disk off the Passport onto the main drive, but I get the error the OP observed. I can create a new snapshot off the base disk, but I cannot move it, nor consolidate the two vmdks into one on the main drive.3 I would like to move the base vmdk off the Passport onto the main drive, but I get the error the OP observed. I can create a new snapshot off the base vmdk, but I cannot move it, nor consolidate the two vmdks into one on the main drive. 4 4 5 One theory: The virtual size of the base disk is 477+GB; it only occupies 23GB. Yet there is "only" about 445GB free on the main drive. Could the VMM be making the silly mistake of rejecting the move because the *virtual* size of the media to move is greater than the free space on the destination?5 One theory: The virtual size of the base vmdk is 477+GB; it only occupies 23GB. Yet there is "only" about 445GB free on the main drive. Could the VMM be making the silly mistake of rejecting the move because the *virtual* size of the media to move is greater than the free space on the destination? 6 6 7 7 Per the suggestion, I searched the forums for different forms of this topic, including the error code. No dice.

