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

After repeated SAN path failovers, operations that involve VMFS changes might fail for all hosts accessing a particular LUN (1009899)

  • 2 Ratings

Symptoms

  • On rare occasions, after repeated path failovers to a particular SAN LUN, attempts to perform such operations as VMFS datastore creation and vMotion may fail on all ESX/ESXi hosts accessing this LUN.
  • In the log files, you see the warning:

    I/O failed due to too many reservation conflicts.
    Reservation error: SCSI reservation conflict

  • In ESXi 4.1, you see an error similar to:

    WARNING: FS3: 7096: Reservation error: Timeout

Cause

If you see the reservation conflict messages on all hosts accessing the LUN, this indicates that the problem is caused by the SCSI reservations for the LUN that are not completely cleaned up and no host can use the LUN.

Resolution

This is a known issue affecting VMware 4.x and 5.1.x.

Currently, there is no resolution

To work around this issue, remove the SCSI reservation by running the LUN reset command from any system in the cluster:


vmkfstools -L lunreset /vmfs/devices/disks/device ID

Additional Information

Update History

10/17/2011 - Updated Products to include ESX/ESXi 4.1 12/03/2012 - Updated symptoms for ESXi 4.1

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.

Feedback

  • 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
Actions
KB: