I have an Novell OES2 server (SLES 10 SP1 with Novell add-ons) which I have been using as a NAS server for VM storage on some test ESX servers (ESX 3.0.2 Update 1). It has been working perfectly for me. In order to fully leverage some of the benefits of the OES2 environment I recently deleted the volume I was using for the NFS storage, and recreated it as an NSS volume. Reconfigured NFS and everything seemed fine, except ESX absolutely will not create a VMDK file on this volume. I have tried creating a new VM, migrating a VM, even copying a VMDK using vmkfstools, but all fail.
I have attached some log excerpts and messages from a new VM creation and a VMDK clone using vmkfstools.
I can create a new VM fine via NFS on a non-NSS volume on the same server. And, the funny thing is, if I copy that VM to the NSS volume and add it to the inventory on the ESX server, it works fine. I can run the VM, add and remove snapshots, etc. without any problems. The problems seems to be the actual initial creating of a VMDK file (although that is just my assumption).
This is probably not a supported configuration, but I just can't wrap my head around why it will not work. If anyone has tried this and got it working, or has any suggestions, I would love to hear about it.
Thanks.
TW