I was reading this artictle: https://static.rainfocus.com/vmware/vmw ... 01nYO0.pdf
Which is a presentation from vmWorld 2017 entitled "A Deep Dive into vSphere 6.5 Core Storage Features and Functionality [SER1143BU]"
I got to side 18 which was talking about differences between VMFS6 and VMFS5:
Resources for VMs (blocks, file descriptors, etc.) on earlier VMFS versions were
allocated on a per host basis (host-based block allocation affinity)
• Host contention issues arose when a VM/VMDK was created on one host, and then
vMotion was used to migrate the VM to another host
• If additional blocks were allocated to the VM/VMDK by the new host at the same time
as the original host tried to allocate blocks for a different VM in the same resource
group, the different hosts could contend for resource locks on the same resource
• This change introduces VM-based block allocation affinity, which will decrease
resource lock contention
I checked -- the datastores that the replicas are in a vmWare 6.5 VM on Server 2012 ReFS stored on *VMFS5*.
Any chance this is the issue? Ugly if it is because there is no easy conversion from VMFS5 to VMFS6 other than "get a new datastore (on additional storage you may not have), and then move the data from the old VMFS5 datastore to the new one".
I thought this because VMFS6 comes WITH 6.5..... So what about old VMFS5 datastores..... from text above they could be having resource lock contention --- that's what the error sounds like.
What do you think?