Hello. I can't bring online physical disk resources on my MSCS 2003 build upon ESX 3.5 host. Let me bring up some more details about the infrastructure.
My ESX 3.5 U4 host works in standalone mode (no VC whatsoever). All VM's are stored on NetApp filer and my host doesn't use direct connection to it through HBA (like iSCSI). It is rather connected to the NFS share hosted on that filer. This is not my first approach to install MSCS within virtual environment, but first time in such scenario. I created folder on the filer and three vmdk files as shared cluster resources underneath using following command:
vmkfstools -c size -d eagerzeroedthick -a lsilogic path_to_vmdk_file
Next i added these resources to one of my cluster nodes, on separate LSI SCSI controller set to virtual mode (to share resource between nodes).
Everything worked fine until cluster wizard went into second stage (tried to bring online physical disks). I tried to go more deeply into that problem, and i decided to create dummy shared disk on local storage. When i did that I was able to bring this resource online successfully. I tried to use disk.locking = "false" option - no success. I double checked permissions on NFS - no issues, ran chmod and chown agains my cluster resource files. Finaly i opened Device Manager and played with Cluster Disk Service (Driver) under Non-Plug and Play device node section. It looks like this driver is responsible for the management of physical disk resources - locks and frees them. I don't have a clue what might cause this problem. Help appreciated:)
Thanks.
MSCS on NFS is not supported. And this wouldn't even work for long time even if you tweak the vmx file.
Please refer MSCS guide for same (http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_mscs.pdf, page: 16)
You are trying something which will not work.
Thanks,,
Ramesh. Geddam,
VCP 3&4, MCTS(Hyper-V), SNIA SCP.
Please award points, if helpful
Thanks for your reply. Presumably i stuck with either RAW disk mapping or local storage?
Thanks for clarify this for me, mate. I should read more carefully manuals and white papers:)