Files remain in source datastore after Storage vMotion

Recently I did Storage vMotion on a few servers in vSphere 6.0  and  noticed the same files  remain in the source and destination datastore.  I  find this behaviour confusing, since I was expecting the source datastore to delete all the files automatically after the sVM.

Any idea why this happens and how to fix this going forward.
Who is Participating?
Ajay ChananaMCSE-2003/08|RHCSA| VCP5/6 |vExpert2018Commented:
To avoid confusion you may try consolidating the VM. This will remove snapshot and if you still find the  files those are orphan.

Usually if you migrate the VM what so ever is not associated with VM will be leftover. If it is associated and not able to move then your storage vMotion will not be completed.

You may also try touch command to see if those files are in use. Go to VM directory type "touch * " see if those files are busy.

For sure those leftovers are orphan files.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Normal behaviour after a storage vMotion, some files can be left behind, BUT check which ones are in use!

and you can then dispose of the orphans.
cgeorgeisaacAuthor Commented:
I think it is orphaned files.  Mostly it is "slots" and few delta files.
How can I find out if these files are in use?  I did not find these files in the new (destination) datastore.
Unable to delete.  SOIC is not enabled.    
Is there an easier way to delete these files.
Not too sure if rebooting the EXSi Host will help.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.