Hello all :
I'm doing VSAN cert. i run into below problem when i try to create or clone a vm in vsandatastore:
The failed stack:
The policy requires 2 replicas with 1 disks each with 0 bytes free each. Only found 0 such disks.
Failed to create object:
other information:
VC build: 1750787
Error Type: CannotCreateFile
Task ID: Task
Description ID: Folder.createVm
Event Link ID: 188
Hardware description:
Server : Lenovo ThinkServer RD440
I/O Controller: LSI 9270CV-8i
HDD: Seagate ST600MM0006
SSD: Intel SSDSC2BB300G4
esxcli vsan policy getdefault:
Policy Class Policy Value
------------ --------------------------------------------------------
cluster (("hostFailuresToTolerate" i1))
vdisk (("hostFailuresToTolerate" i1))
vmnamespace (("hostFailuresToTolerate" i1))
vmswap (("hostFailuresToTolerate" i1) ("forceProvisioning" i1))
i really don't know how to resolve the promlem, please hlep give me some suggestions.
Thanks in advance
Can you drill down into each of your disk groups and verify that all your disks on each host are healthy?
Hello CHogan
Thanks for your reply.
The problem has been resolved after i define and enable Virtual Machine Storage Policies.
By the way, it must use the Virtual Machine Storage Policies for VSAN?
when the problem occurs, the Storage Policies is none.
Thanks and Regards
Hexy
Although it is really recommended to use the storage policies, it is actually not required.
What happens is that deploying a VM, without any storage policy, onto a VSAN datastore sets the objects to Failure To Tolerate = 1 by default.
See example:
What version are you running? You might want to doublecheck that all hosts' VMKernel interfaces are configured with Virtual SAN traffic service enabled.
\Ibrar
That's a bit strange. The major difference between the default (None) policy and a user-created policy is the VM provisioning. With a user create policy, the object space reservation will be 0%, effectively creating a thin disk.
With the default None policy, the disk format is selected via the VM creation wizard, which will use lazy zero thick by default (LZT).
Maybe that has something to do with the fact that you could roll out the VM... do you have enough disk space in your VSAN cluster?