register
Contributor
Contributor

VMDK file on Flexclone vol will not mount unless original VM is powered down???

I hope someone can explain this to me. I run my VMs from NFS mounts on NetApp Filers. I wanted to recover some files from a previous night's snapshot, so I made a flexclone volume from the snapshot, mounted that, and added the .vmdk disk file from the flexclone snapshot to another VM. I also removed the Lock file from the flexclone snapshot. I continued to get the errors below until I powered off the original VM. The flexclone is a separate, Read/Write copy. Why can't the .vmdk copy be opened and read while the original is running? Is there another step I need to take?

This is from the vmware.log.

Dec 09 09:04:43.205: vmx| HotAdd: Adding disk '/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32.vmdk' with mode 'persistent' to scsi0:1

Dec 09 09:04:43.205: vmx| DISK: OPEN scsi0:1 '/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32.vmdk' persistent R[(null)]

Dec 09 09:04:43.209: vmx| DISKLIB-VMFS : "/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32-flat.vmdk" : failed to open (1048585): AIOMgr_Open failed. Type 3

Dec 09 09:04:43.209: vmx| DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode

Dec 09 09:04:43.209: vmx| DISKLIB-LINK : "/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32.vmdk" : failed to open (Device or resource busy).

Dec 09 09:04:43.209: vmx| DISKLIB-CHAIN : "/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32.vmdk" : failed to open (Device or resource busy).

Dec 09 09:04:43.209: vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32.vmdk' with flags 0xa (Device or resource busy).

Dec 09 09:04:43.209: vmx| DISK: Cannot open disk "/vmfs/volumes/54b7e8aa-72824e19/hqs32/hqs32.vmdk": Device or resource busy (1048585).

0 Kudos
1 Reply
RParker
Immortal
Immortal

Why can't the .vmdk copy be opened and read while the original is running? Is there another step I need to take?

Well apparently the VM is associated with the clone. Rename it while the VM is down, and see what happens when you try to power it on.. it THINKS that's the current vmdk file.

0 Kudos