SCSI: 5541: Failing I/O due to too many reservation conflicts

[stephen_f]

Hello,

I noticed these error messages in the vmkwarning log on one of my ESX host running version 3.0.1, 42829.

Oct 22 11:24:24 vmkernel: 48:07:58:17.029 cpu3:1038)WARNING: SCSI: 5637: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:2. residual R 919, CR 0, ER 3

Also, when I am connected to the ESX host via the VI client and click on the Configuration tab - Storage (SCSI,SAN and NFS), one of the LUN will give the following error:

"Timed out waiting for the server response."

I click "OK" then I get

"Object reference not set to an instance of an object."

Also, no information showing in the Details section of the screen.

Any help will be greatly appreciated. Thanks.

[TCronin]

What type of SAN, and what make/model of HBA?

There are some SAN's and HBA's that do require specific settings.

[stephen_f]

SAN - HP EVA 6000

HBA - Emulex LP1150

I didn't build these ESX servers but I do have another ESX host with identical hardware config and it is not experience the same issue. I can always compare the configuration if I know what to look for. Thanks!

[w_1]

Hi Stephen

I see the log is old, Did you manage to fix the issue

Thanks

[stephen_f]

As of right now the issue went away. I tried replacing the fiber cable but that didn't resolve it. Then I upgraded the ESX server from 3.01 to 3.02 and that didn't fix it either. Finally I found a post on VMTN and someone mentioned something about database being too big and causing a delay. I didn't think it will help because I have 2 ESX servers both connecting to the same storage and it is happening on one but not the other. I decided to try it anyway and ran a sql command to truncate the history table. It's been working ever since.

[kastro]

I have the same problem/config. But errors only on RDM LUNs and only on one host.

Jan 9 14:02:47 mzzesx2 vmkernel: 28:18:46:04.444 cpu2:1046)WARNING: SCSI: 5519: Failing I/O due to too many reservation conflicts

Jan 9 14:02:47 mzzesx2 vmkernel: 28:18:46:04.444 cpu2:1046)WARNING: SCSI: 5615: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:3. residual R 919, CR 0, ER 3

Jan 9 14:02:52 mzzesx2 vmkernel: 28:18:46:09.508 cpu1:1046)WARNING: SCSI: 5519: Failing I/O due to too many reservation conflicts

Jan 9 14:02:52 mzzesx2 vmkernel: 28:18:46:09.508 cpu1:1046)WARNING: SCSI: 5615: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:4. residual R 919, CR 0, ER 3

Jan 9 14:02:57 mzzesx2 vmkernel: 28:18:46:14.497 cpu0:1045)WARNING: SCSI: 5519: Failing I/O due to too many reservation conflicts

Jan 9 14:02:57 mzzesx2 vmkernel: 28:18:46:14.497 cpu0:1045)WARNING: SCSI: 5615: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:5. residual R 919, CR 0, ER 3

[Faustina]

There is an issue with the way the SAN configuration is setup look at the resignaturing section in the san config guide and ensure that the configuration is as per the vmware requirements.

[knoxvegas31]

Did you ever get this resolved? I'm in the same boat as you are or were. Thanks.

[Texiwill]

Hello,

SCSI Reservations are made anytime the metadata of a file on a VMFS is modified. That includes whenever files are opened, closed, have access, create, modification times changes, grow in size, etc.

They can also happen when the SAN is overloaded and response times are slower due to traffic where it then takes longer for everything. Check out this Excerpt from my book that covers most of the subject in detail.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll

Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links