Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Analyzing SCSI Reservation conflicts on VMware Infrastructure 3.x, vSphere 4.x, vSphere 5.x and vSphere 6.0 (1005009)

Last Updated: 4/14/2017Categories: TroubleshootingTotal Views: 103406Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Details

ESX 3.x or ESX 4.x VMkernel logs contain these messages:

SCSI: vm 1043: 5522: Sync CR at 64
SCSI: vm 1043: 5522: Sync CR at 48
SCSI: vm 1043: 5522: Sync CR at 32
SCSI: vm 1043: 5522: Sync CR at 16
SCSI: vm 1043: 5522: Sync CR at 0
WARNING: SCSI: 5532: Failing I/O due to too many reservation conflicts
WARNING: SCSI: 5628: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:7. residual R 919, CR 0, ER 3
WARNING: J3: 1970: Error committing txn to slot 0: SCSI reservation conflict

ESXi 4.x, ESXi 5.x and ESXi 6.0 vmkernel logs contains below messages

Vendor: EMC Model: SYMMETRIX Rev: 5771
Type: Direct-Access ANSI SCSI revision: 03
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
sdh : READ CAPACITY failed.
status = c, message = 00, host = 0, driver = 00
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
scsi0 (0,0,52) : RESERVATION CONFLICT
VMWARE: Device that would have been attached as scsi disk sdh at scsi0,channel 0, id 0, lun 52 Has not been attached because this path could not complete a READ command eventhough a TUR worked.result = 0x18 key = 0x0, asc = 0x0, ascq = 0x0
VMWARE: Device that would have been attached as scsi disk sdh at scsi0,channel 0, id 0, lun 52 Has not been attached because it is a duplicate path or on a passive path
scan_scsis starting finish
scan_scsis done with finish

Solution

Note: The Atomic Test and Set (ATS) primitive is used for locking on Virtual Machine File System (VMFS) datastores for VMware vSphere Storage APIs for Array Integration (VAAI) compatible storage arrays. It is far superior to the SCSI Reservation locking technique. For more information on VAAI, see Frequently Asked Questions for vStorage APIs for Array Integration (1021976).

There are two main categories of operation under which VMFS makes use of SCSI reservations.

Category 1: is for VMFS data-store level operations. These include opening, creating, resignaturing, and expanding/extending of VMFS data-store.

Category 2: involves the acquisition of locks. These are locks related to VMFS specific meta-data (called cluster locks) and locks related to files (including directories). Operations in the second category occur much more frequently than operations in the first category.

These are some examples of VMFS operations that require locking metadata:

Creating a VMFS datastore

Expanding a VMFS datastore onto additional extents

Powering on a virtual machine

Acquiring a lock on a file

Creating or deleting a file

Creating a template

Deploying a virtual machine from a template

Creating a new virtual machine

Migrating a virtual machine with vMotion

Growing a file, for example, a snapshot file or a thin provisioned virtual disk

For the zeroed thick type of virtual disk the reservation is required only when zeroing the blocks.

If the VMware VMkernel log contains the messages described in the Details section, perform these procedures:

If the VMware ESX version is:

3.0.1, install Patch ESX-1002960: Fix for SCSI Reservation Conflict Issue. For more information, see ESX Server 3.0.1, Patch ESX-1002960: Fix for SCSI Reservation Conflict Issue (1002960).

3.0.2, install Patch ESX-1002974: Fix for SCSI Reservation Conflicts. For more information, see ESX Server 3.0.2, Patch ESX-1002974: Fixes for SCSI Reservation Conflicts; Support for EMC Invista (1002974).

If the log messages persist and the ESX host is running on an HP Server using Insight Manager Agents, see Insight Manager may cause SCSI reservation conflicts (1004771).

If the log messages persist, see the article that applies to your environment:

SCSI Reservation Failures on HDS USP and NSC (1005010)

SCSI Reservation Failures on HP XP Storage Arrays (1005011)

SCSI Reservation Failures on Hitachi USP and NSC Arrays (1006001)

SCSI Reservation Failures on SUN StorageTek 9985 and 9990 Arrays (1006002)

SCSI Reservation Failures on Nihon Unisys SANARENA 5200 and 5800 Arrays (1006003)

Virtual machines may experience I/O failures due to too many SCSI reservation conflicts on some 3PAR arrays (1020366)

Note: The list of arrays is not exhaustive and is to be revised when other arrays are identified reporting these errors.

Follow these steps to resolve potential sources of the reservation:

Try to serialize the operations of the shared LUNs. If possible, limit the number of operations on different hosts that require SCSI reservation at the same time.

Increase the number of LUNs and try to limit the number of ESX hosts accessing the same LUN.

Reduce the number of snapshots as they cause a lot of SCSI reservations.

Do not schedule backups (VCB or console based) in parallel from the same LUN.

Schedule antivirus or operating system updates outside normal business hours so that it does not interfere with daily operations.

Try to reduce the number of virtual machines per LUN. For more information, see:

ESXi 6.0: Configuration Maximums

ESXi 5.5: https://www.vmware.com/pdf/vsphere5/r55/vsphere-55-configuration-maximums.pdf

ESXi 5.1: https://www.vmware.com/pdf/vsphere5/r51/vsphere-51-configuration-maximums.pdf

ESXi 5.0: http://www.vmware.com/pdf/vsphere5/r50/vsphere-50-configuration-maximums.pdf

ESXi/ESX 4.1: http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf

ESXi/ESX 4.0: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf

ESXi/ESX 3.5: http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_config_max.pdf

6.

Determine what targets are being used to access the LUNs.

Check if you have the latest HBA firmware across all ESX hosts.

Ensure that the ESX is running the latest BIOS (to avoid conflict with HBA drivers).

Contact your SAN vendor for information on SP timeout values and performance settings and storage array firmware.

Turn off third-party agents (storage agents) and RPMs not certified for ESX.

Disable any encryption re-keying on the fiber channel switches, as this can cause loss of access for more than 60 seconds.

Check for MSCS RDMs (active node holds permanent reservation). For more information, see ESX servers hosting passive MSCS nodes report reservation conflicts during storage operations (1009287).

Ensure that you have selected the correct Host Mode setting on the SAN array.

Rescan. LUNs removed from the system without rescanning can appear as locked.

Look for failed SPs. When SPs fail to release the reservation, either the request did not come through (hardware, firmware, pathing problems) or third-party apps running on the service console did not send the release. Busy virtual machine operations are still holding the lock.

Note: Use of SATA disks is not recommended in high I/O configuration or when the above changes do not resolve the problem while SATA disks are used.

If your array is not listed above and none of the above points eliminate the log messages, file a Support Request with VMware Support and note this KB Article ID (1005009) in the problem description. For more information, see Filing a Support Request in Customer Connect (2006985).

Additional Information
For translated versions of this article, see:

Español: Análisis de conflictos de reserva de SCSI en VMware Infrastructure 3.x, vSphere 4.x y vSphere 5.x (2046732)

Português: Como analisar os conflitos de Reserva de SCSI no VMware Infrastructure 3.x, vSphere 4.x e vSphere 5.x (2046060)

日本語: VMware Infrastructure 3.x および vSphere 4.x での SCSI 予約競合の分析 (1033285)

简体中文: 分析 VMware Infrastructure 3.x、vSphere 4.x 和 vSphere 5.x 上的 SCSI 预留冲突 (2086595)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant