We are testing vsphere with NFS storage. We are using CentOS 5.3 with exts as well as Fedora 12 with ext4 file system. At the time of VM creation,
it is grayed out both options "enable FT" & "thin provision". It looks like NFS server is selecting the VM hdd space itself. Which OS which we should
use to correct this problem?
Regards,
Swapnil M
Message was edited by: scottm123
In this case don't worry.
You have thin disks.
FT is not enabled at disk level (it's only a requirement), cause you have to enable (if you need) at VM level.
Andre
Usually with NFS the vmdk are in thin format.
It's a limit of NFS datastore.
For this reason you cannot enable FT, cause it required a special type of thick disk.
Andre
If the purpose only for Fault Tolerance, you dont have to worry since FT support shared storage using NFS. Plus, all VM's vmdk will automatically converted to eagerzeroedthick disk once you enable for fault tolerance. However, you need to power off the VM first and convert your NFS vmdk from thin to thick using "inflate" (right click your VM .vmdk in datastore) button or by using vmkfstools.
FT on NFS KB http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1010631&sl... 0 96651876
FT enable convert to eagerzeroedthick KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100986...
vcbMC-1.0.6 Beta
vcbMC-1.0.7 Lite
I think I've posted a wrong question. After selecting NFS storage, by default it is selecting both the
options "Allocate and commit space on demand (Thin Provisioning)" + "Support clustering features such as Fault Tolerance".
We only want thin provisiong and not FT.
Regards,
Scott
In this case don't worry.
You have thin disks.
FT is not enabled at disk level (it's only a requirement), cause you have to enable (if you need) at VM level.
Andre