VMware Communities > VMTN > VMware Infrastructure™ > VI: ESX 3.5 > Discussions
Up to Discussions in VI: ESX 3.5

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
2 Replies Last post: Oct 26, 2007 8:33 AM by radu.dinut
Reply

Attach raw device already used by a physical server - cluster between them

Oct 25, 2007 1:45 PM

Click to view radu.dinut's profile Enthusiast radu.dinut 36 posts since
Aug 31, 2007

Hi guys.

I have a problem. I have a physical server which I cannot shutdown right now. The second node is supposed to be virtual. I'm using ESX 3.0.2, w2k3 sp2. The devices are already presented to both systems - physical windows and ESX. The physical one is already up&running as one node of the active-pasive cluster. I need to attach the raw devices to the virtual machine on ESX, too. The error is: "Operation failed due to concurrent modification by another operation."

Any ideas?

Tags: windows, vmfs, path, luns, configuration, 3.0.2
Reply Re: Attach raw device already used by a physical server - cluster between them Oct 25, 2007 6:04 PM
Click to view Rumple's profile Master Rumple 1,245 posts since
Jan 6, 2005

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1862&sliceId=1&docTypeID=DT_KB_1_1&dialogID=28292008&stateId=0%200%2028290102

This what is happening?

Reply Re: Attach raw device already used by a physical server - cluster between them Oct 26, 2007 8:33 AM
in response to: Rumple
Click to view radu.dinut's profile Enthusiast radu.dinut 36 posts since
Aug 31, 2007

Hi.

I have all those errors. But...

These are my volumes:

471f52da-d332b8d5-75f4-00132107ee09 storage1 (3)
472103b3-190ce1f5-33f9-00132107ee09 xpst_rdcro01app101_ro_01
472103b3-25629fff-5343-00132107ee09 xpst_rdcro01app101_ro_02

This is what I have in disks:

root@rdcro01wmx114 volumes# cd /vmfs/devices/disks
root@rdcro01wmx114 disks# ls
vmhba0:0:0:0 vml.020000000060060e80042aa40000002aa40000041d4f50454e2d56
vmhba1:0:0:0 vml.020001000060060e80042aa40000002aa4000006224f50454e2d56
vmhba1:0:1:0 vml.020002000060060e80042aa40000002aa400000caa4f50454e2d56
vmhba1:0:2:0 vml.020003000060060e80042aa40000002aa400000cab4f50454e2d56
vmhba1:0:3:0

This is the command:

root@rdcro01wmx114 volumes# vmkfstools -L lunreset /vmfs/devices/disks/vmhba1:0:2:0 ; vmkfstools -z /vmfs/devices/disks/vmhba1:0:2:0 /vmfs/volumes/test2.vmdk
GetFreeSpace: ioctl on /vmfs/volumes/test2.vmdk failed with 38 -1
Failed to create virtual disk: Function not implemented 2490377

I'm not even sure what that means or if I understood corectly that article. The thing is I don't understand what's with that .vmdk file, I need a raw device, accessed directly by the virtual machine, not as storage to ESX host.

Actions
Up to Discussions in VI: ESX 3.5