Search the VMware Knowledge Base (KB)
View by Article ID

vSAN 6.2 hybrid disk group performance degradation (2146267)

  • 2 Ratings
Language Editions


  • After upgrading a vSAN (Formerly known as Virtual SAN) environment with Hybrid disk groups to version 6.2, some virtual machines resident on vSAN datastores may exhibit poor disk IO performance compared to previous versions of  vSAN.

    For example, Virtual Machine Read and/or Write IOs may have poor response time than on vSAN 6.1 or vSAN 6.0.
  • A significantly lower than expected read cache hit ratio is observed on vSAN caching tier.
  • A higher percentage of IOPS may be observed on capacity tier disks (Magnetic disks) on Hybrid diskgroups when compared to vSAN 6.0 or vSAN 6.1 systems.


The vSAN 6.2 performance issue with hybrid disk groups is resolved in VMware ESXi 6.0 Patch Release ESXi600-201608001.

A hybrid disk group comprises of one Solid State Disks (SSD) for the cache tier and one or more Magnetic HDDs (MDs) for the Capacity tier.


In vSAN 6.2, new data services are introduced. One of these data services is Deduplication and Compression. Deduplication and Compression are not supported for Hybrid vSAN configurations. 

This issue is caused by vSAN 6.2 performing low level scanning for unique blocks, which is related to deduplication, can still occur on vSAN hybrid disk groups. This causes performance deterioration on Hybrid Disk groups, as it has a significant read caching performance impact on the SSD cache tier of vSAN disk groups.


This issue affects vSAN 6.2 Hybrid deployments only. This issue is NOT applicable to All Flash vSAN Clusters.

This issue is resolved in VMware ESXi 6.0 Patch Release ESXi600-201608001 available at VMware Patch Downloads. For more information, see:

To work around this issue if you do not want to upgrade, VMware advises to turn off the dedup scanner option on each vSAN node contributing to a vSAN Hybrid cluster.

  • A vSAN node must be placed in maintenance mode (with the Ensure Accessibility option) and a restart is required.
  • These commands must be run on each ESXi host in the vSAN cluster.
  • These commands result in persistent changes and remain configured across reboots.

To disable the dedup scanner:
  1. Connect to your ESXi vSAN cluster  node using the ESXi Shell.
  2. Run this command to turn off the dedup scanner:

    esxcfg-advcfg -s 0 /LSOM/lsomComponentDedupScanType

  3. Verify the new setting using this command:

    esxcfg-advcfg -g /LSOM/lsomComponentDedupScanType

    • For Hybrid vSAN deployments, the value of lsomComponentDedupScanType is 0 when disabled.
    • The default value for lsomComponentDedupScanType is 2.

  4. To apply the new setting on a vSAN Cluster, select the Ensure Accessibility option and place each host in maintenance mode.

  5. Reboot each host or node in a rolling fashion to ensure vSAN objects remain available.

    Note: The requirement for a reboot is to ensure any active dedup scanning session of existing data will be terminated in a consistent manner across a given cluster.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box. 

The advanced option lsomComponentDedupScanType is not available on the vSphere WebClient, but it can be modified using PowerCLI (or other compatible vSphere API clients) for orchestration purposes.

Example PowerCLI code  to disable dedup scanner on vSAN Hybrid diskgroups:

Get-VMHost yourhostname | Get-AdvancedSetting -Name LSOM.lsomComponentDedupScanType |Set-AdvancedSetting -Value "0"

To verify the setting, you can use a PowerCLI code.


Get-VMHost yourhostname | Get-AdvancedSetting –Name LSOM.lsomComponentDedupScanType

See Also

Language Editions


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 2 Ratings