Code: Select all
esxcli system settings advanced set -i 0 -o /VMFS3/HardwareAcceleratedLocking
Synology support bounced emails back and forth with me for a week, then finally revealed that this was a known issue, and said:
After speaking with out developers it appears that this is a know issue.
In before DSM 5.2 we provided the wrong ATS information and that issue has since be corrected in DSM 6.0+.
However, remounting the original LUN may experience such issue.
As for other LUNs, the ATS feature of other LUNs may show correctly in the VMware before DiskStation upgrade to DSM6.0, however, we can't confirm right now.
So what we can do at the moment is help confirm you are able to mount the iscsi LUN without problem, and ATS feature of all LUNS is showing correctly in the VMware.
This read to me that it was supposed to be fixed in 6.0+, but they replied that all they could do to help was what I had already done to turn of ATS locking. There was no ETA of a fix, and per the developers:
So basically, it seems that as long as you are able to mount the LUN successfully that is all that they are able to do currently, but they are aware of the situation.
Needless to say, both me as a reseller and my customer are mortified at this lack of support. The RC- platform has been fraught with problems since we bought it, from hourly reboots during the first 3 months of its life to now not even supporting advanced locking, thus slowing down all the LUNs on the whole host. Be careful - I for one have little choice but to relegate what I was hoping to be the new low cost SAN for 2-3 node VMware clusters back to the back burner for backup and secondary storage duty.