Storage vmotion issue with VM - Persistent Independent Disk

[java_cat33]

Hi - I've just been storage vmotioning some VM's....... this one VM in particular had a persistent independent disk which I did not realise...... as a consequence the disk migrated to the new vmfs datastore however the dmotion file still resides on the old lun. The disk within the settings of the VM still references the old lun.

My question is this - Can I power off the VM and turn off the settings for this disk to be independent.... power the VM back on and then the dmotion vmdk will then commit to the base? Where to from here to get my desired end result?

I don't want to make that change to the disk since there is a dmotion file in place without knowing if there will be any consequences.

Thanks

[java_cat33]

Well I've sorted it - for those who want to know..... I removed the disk from the VM and added the disk that was moved to the new vmfs volume (in a non persistent state!). The dmotion file doesn't get committed to the base due to the fact the disk was originally in persistent mode - it simply needs to be deleted.