VMware Cloud Community
fcarvalho
Contributor
Contributor
‎11-22-2007 11:36 AM

SCSI Reservation Conflit

Hello

I have ESX server with QLA2422 and QLA2432.

When I rescan an HBA give me this kind of errors:

Nov 22 18:42:24 XXXXXXXXX vmkernel: 0:00:28:09.125 cpu6:1037)WARNING: SCSI: 5529: Failing I/O due to too many reservation conflicts

Nov 22 18:42:24 XXXXXXXXX vmkernel: 0:00:28:09.125 cpu6:1037)WARNING: SCSI: 5625: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:10.

I already try this:# esxcfg-module -s ql2xlogintimeout=5 qla2300_707

# esxcfg-boot -b

# reboot

Any help??

Thanks

0 Kudos
8 Replies
Dave_Mishchenko
Immortal
Immortal
‎11-22-2007 11:48 AM

this thread might help - http://communities.vmware.com/thread/84390

fcarvalho
Contributor
Contributor
‎11-22-2007 02:41 PM

Hello Dave

Thanks for you help but didn't work.

This error occurred on RDM LUN

Thanks

I attach more log's.

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Supported VPD pages for vmhba2:0:0 : 0x0 0x80 0x83 0x85 0xc0

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Device id info for vmhba2:0:0: 0x1 0x3 0x0 0x10 0x60 0x6 0x1 0x60 0x8f 0x91 0x1c 0x0 0xf6 0x11 0xb0 0x25 0x20 0x47 0xdc 0x11 0x1 0x0 0x0 0x10 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x36 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x14 0x0 0x4 0x0 0x0 0x0 0x7 0

Nov 22 21:53:07 vmkernel: x1 0x15 0x0 0x4 0x0 0x0 0x0 0x2

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Id for vmhba2:0:0 0x60 0x06 0x01 0x60 0x8f 0x91 0x1c 0x00 0xf6 0x11 0xb0 0x25 0x20 0x47 0xdc 0x11 0x52 0x41 0x49 0x44 0x20 0x35

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Supported VPD pages for vmhba2:0:1 : 0x0 0x80 0x83 0x85 0xc0

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Device id info for vmhba2:0:1: 0x1 0x3 0x0 0x10 0x60 0x6 0x1 0x60 0x8f 0x91 0x1c 0x0 0xd2 0x95 0xc8 0xa9 0x28 0x47 0xdc 0x11 0x1 0x0 0x0 0x10 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x37 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x14 0x0 0x4 0x0 0x0 0x0 0x7 0

Nov 22 21:53:07 vmkernel: x1 0x15 0x0 0x4 0x0 0x0 0x0 0x2

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Id for vmhba2:0:1 0x60 0x06 0x01 0x60 0x8f 0x91 0x1c 0x00 0xd2 0x95 0xc8 0xa9 0x28 0x47 0xdc 0x11 0x52 0x41 0x49 0x44 0x20 0x35

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Supported VPD pages for vmhba2:0:2 : 0x0 0x80 0x83 0x85 0xc0

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Device id info for vmhba2:0:2: 0x1 0x3 0x0 0x10 0x60 0x6 0x1 0x60 0x8f 0x91 0x1c 0x0 0xf2 0xe6 0x41 0xb5 0x28 0x47 0xdc 0x11 0x1 0x0 0x0 0x10 0x0 0x2 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x38 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x14 0x0 0x4 0x0 0x0 0x0 0x7 0

Nov 22 21:53:07 vmkernel: x1 0x15 0x0 0x4 0x0 0x0 0x0 0x2

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Id for vmhba2:0:2 0x60 0x06 0x01 0x60 0x8f 0x91 0x1c 0x00 0xf2 0xe6 0x41 0xb5 0x28 0x47 0xdc 0x11 0x52 0x41 0x49 0x44 0x20 0x35

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Supported VPD pages for vmhba2:0:3 : 0x0 0x80 0x83 0x85 0xc0

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Device id info for vmhba2:0:3: 0x1 0x3 0x0 0x10 0x60 0x6 0x1 0x60 0x52 0x91 0x1c 0x0 0x38 0x24 0xef 0x58 0x88 0x81 0xdc 0x11 0x1 0x0 0x0 0x10 0x0 0x3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x40 0x0 0x0 0x0 0x0 0x0 0x0 0x1 0x14 0x0 0x4 0x0 0x0 0x0 0x7 0

Nov 22 21:53:07 vmkernel: x1 0x15 0x0 0x4 0x0 0x0 0x0 0x2

Nov 22 21:53:07 vmkernel: VMWARE SCSI Id: Id for vmhba2:0:3 0x60 0x06 0x01 0x60 0x52 0x91 0x1c 0x00 0x38 0x24 0xef 0x58 0x88 0x81 0xdc 0x11 0x52 0x41 0x49 0x44 0x20 0x35

Nov 22 21:53:15 vmkernel: 1:04:29:54.090 cpu2:1038)SCSI: 8311: Finished rescan of adapter vmhba2

Nov 22 21:53:15 vmkernel: 1:04:29:54.716 cpu5:1056)<6>dpc(1): qla2x00: RESCAN .

Nov 22 21:53:15 vmkernel: 1:04:29:54.733 cpu5:1056)<6>dpc(1): qla2x00: RESCAN... done.

Nov 22 21:53:15 vmkernel: 1:04:29:54.970 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 64

Nov 22 21:53:15 vmkernel: 1:04:29:55.917 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 48

Nov 22 21:53:15 vmkernel: 1:04:29:56.900 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 32

Nov 22 21:53:15 vmkernel: 1:04:29:57.896 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 16

Nov 22 21:53:15 vmkernel: 1:04:29:58.892 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 0

Nov 22 21:53:15 vmkernel: 1:04:29:58.892 cpu2:1038)WARNING: SCSI: 5529: Failing I/O due to too many reservation conflicts

Nov 22 21:53:15 vmkernel: 1:04:29:58.892 cpu2:1038)WARNING: SCSI: 5625: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba2:0:0. residual R 919, CR 0, ER 3

Nov 22 21:53:15 vmkernel: 1:04:29:58.892 cpu2:1038)SCSI: 6618: Partition table read from device vmhba2:0:0 failed: SCSI reservation conflict (0xbad0022)

Nov 22 21:53:15 vmkernel: 1:04:29:59.867 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 64

Nov 22 21:53:16 vmkernel: 1:04:30:00.833 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 48

Nov 22 21:53:16 vmkernel: 1:04:30:01.827 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 32

Nov 22 21:53:16 vmkernel: 1:04:30:02.803 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 16

Nov 22 21:53:16 vmkernel: 1:04:30:03.823 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 0

Nov 22 21:53:16 vmkernel: 1:04:30:03.823 cpu2:1038)WARNING: SCSI: 5529: Failing I/O due to too many reservation conflicts

Nov 22 21:53:16 vmkernel: 1:04:30:03.823 cpu2:1038)WARNING: SCSI: 5625: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba2:0:1. residual R 919, CR 0, ER 3

Nov 22 21:53:16 vmkernel: 1:04:30:03.823 cpu2:1038)SCSI: 6618: Partition table read from device vmhba2:0:1 failed: SCSI reservation conflict (0xbad0022)

Nov 22 21:53:17 vmkernel: 1:04:30:04.737 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 64

Nov 22 21:53:18 vmkernel: 1:04:30:05.715 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 48

Nov 22 21:53:19 vmkernel: 1:04:30:06.653 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 32

Nov 22 21:53:20 vmkernel: 1:04:30:07.620 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 16

Nov 22 21:53:21 vmkernel: 1:04:30:08.651 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 0

Nov 22 21:53:21 vmkernel: 1:04:30:08.651 cpu2:1038)WARNING: SCSI: 5529: Failing I/O due to too many reservation conflicts

Nov 22 21:53:21 vmkernel: 1:04:30:08.651 cpu2:1038)WARNING: SCSI: 5625: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba2:0:2. residual R 919, CR 0, ER 3

Nov 22 21:53:21 vmkernel: 1:04:30:08.651 cpu2:1038)SCSI: 6618: Partition table read from device vmhba2:0:2 failed: SCSI reservation conflict (0xbad0022)

Nov 22 21:53:22 vmkernel: 1:04:30:09.505 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 64

Nov 22 21:53:23 vmkernel: 1:04:30:10.455 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 48

Nov 22 21:53:24 vmkernel: 1:04:30:11.485 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 32

Nov 22 21:53:25 vmkernel: 1:04:30:12.524 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 16

Nov 22 21:53:26 vmkernel: 1:04:30:13.514 cpu2:1038)SCSI: vm 1038: 5519: Sync CR at 0

Nov 22 21:53:26 vmkernel: 1:04:30:13.514 cpu2:1038)WARNING: SCSI: 5529: Failing I/O due to too many reservation conflicts

Nov 22 21:53:26 vmkernel: 1:04:30:13.514 cpu2:1038)WARNING: SCSI: 5625: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba2:0:3. residual R 919, CR 0, ER 3

0 Kudos
fcarvalho
Contributor
Contributor
‎11-22-2007 03:52 PM

Hello

More information:

vmhba0:0:0 /dev/cciss/c0d0

vmhba2:0:0

vmhba2:0:1

vmhba2:0:2

vmhba2:0:3

vmhba2:0:4

vmhba2:0:5

vmhba2:0:18 /dev/sda

vmhba2:0:19 /dev/sdb

vmhba2:0:20 /dev/sdc

vmhba2:0:21 /dev/sdd

vmhba2:0:22 /dev/sde

vmhba2:0:23 /dev/sdf

vmhba2:0:24 /dev/sdg

vmhba2:0:25 /dev/sdh

vmhba2:0:26 /dev/sdi

vmhba2:0:27 /dev/sdj

vmhba2:0:57 /dev/sdk

vmhba2:0:58 /dev/sdl

vmhba2:0:59 /dev/sdm

vmhba2:2:0 /dev/sdn

vmhba2:2:1 /dev/sdo

vmhba2:2:2 /dev/sdr

vmhba2:2:3 /dev/sds

vmhba2:2:4 /dev/sdt

vmhba2:2:5 /dev/sdu

vmhba2:2:7 /dev/sdv

vmhba2:2:8 /dev/sdw

vmhba2:2:9 /dev/sdx

vmhba2:2:10

vmhba2:2:11

vmhba2:2:12

vmhba2:2:13

vmhba2:2:14

vmhba2:2:15

vmhba2:2:16 /dev/sdp

vmhba2:2:17 /dev/sdq

vmhba2:4:28 /dev/sdz

vmhba2:4:29 /dev/sdaa

vmhba2:4:39 /dev/sdab

Thanks

0 Kudos
giovanni_gallor
Hot Shot
Hot Shot
‎11-22-2007 10:12 PM

Maybe I'm wrong, but from what i understood, having some reservation conflicts at host boot or at hba rescanning could be a normal/expected behaviour.

If multiple hosts have access to the same LUN, could happen that the LUN is found reserved by another host at some time (VMFS volumes are reserved in some operations like VM startup, extending/growing files etc...), RDM LUNs used as MS Cluster shared disks are, instead, always reserved by the owning node, so, if you have them, having a reservation conflict could be expected.

If you have other problems, other than log entries, due to res. conflicts, you can try to raise the Scsi.ConflictRetries value in Advanced Settings to 20 (if it's not already).

fcarvalho
Contributor
Contributor
‎11-23-2007 04:18 AM

Hi

Thanks for your tip but I have tested already.

This RDM are for Cluster.

This kind of error occurred when:

rescan hba

add new storage give me error (time out)

reboot ESX

Any more options??

Thanks

0 Kudos
RussellCorey
Hot Shot
Hot Shot
‎11-23-2007 10:05 AM

When the qla2x00 driver hits a reserved LUN it's unable to scan past it. Hence if you've added storage who's LUN is higher than the reserved LUN you'll hit this issue. I THINK you can work around it by ensuring that any nodes with an active reservation exist on the vmware host you're trying to do the rescan on. If possible, vmotion these nodes to your ESX host experiencing the issue and make sure that your clustered data volume is failed to the vm in question.

Do you have any physical nodes in your MSCS cluster?

0 Kudos
fcarvalho
Contributor
Contributor
‎11-24-2007 09:57 AM

Hello

I don't have any physical nodes in MSCS Cluster. All MSCS are virtual machines with RDM (physical).

This happened in every ESX in my environment.

Thanks

0 Kudos
MathiasR
Enthusiast
Enthusiast
‎02-11-2008 07:42 AM

Russfooman, I don't know if your post helped fcarvalho, but it sure helped me! Your described exactly what my scenario and problem was and how to resolve it. Thank you!

0 Kudos