I was able to go into the vmsn files and remove the optical drive/ISO reference lines from them. Once that was done, simply removing and adding back into inventory removed the old datastore hooks. Pretty sure the ISO file it was looking for was gone before I started here. One of the three VMs that I needed to move had the ISO in the base VM settings. I removed that reference (via the normal/GUI mode) and that also released it's last hook into the old datastore. Glad to get rid of that.
Looking forward to getting rid of the final vmfs 5 datastores in the environment. One VM is left to migrate, which has files in two datastores. The free space on the array will be better once I finish the cleanup since the array still sees a lot of consumption on the smaller of the two datastores.
-------------------------------------------
Original Message:
Sent: Feb 04, 2026 09:33 AM
From: CSpreha
Subject: Remove phantom hooks post svmotion?
Sometimes the Ghost is that there was an ISO mounted in the snapshot, that you can't see now after you've removed the ISO, but are still in a snapshotted state. That bit us a lot when getting us off of a shared datastore we used specifically for ISOs.
Original Message:
Sent: Feb 03, 2026 10:03 AM
From: Adam Goldberg
Subject: Remove phantom hooks post svmotion?
I'm in the process of vacating old (vmfs 5) datastores, moving to vmfs 6 datastores on the same array. Out of all of the VMs I've migrated, three still have something hooking them into the old datastore post migration. None of them have iso files (for the cd drive) on the old datastore, nor anything else that I can locate via the GUI. Is there some command I can run against the VM that will show me where these bastards are still tied to the old datastore?
For additional information, these are Citrix VM masters with snapshots present. I did move another VM in the same state (snapshots present) without any issue. It released the old datastore fully post migration, as I expected.
The hosts are running ESXi 7.0.3 build 24723872 for more reference. We are not able to go to a newer version at this time due to the hardware.
-------------------------------------------