getting lots of these on an ESX. any ideas?
Hello,
Yes, generally it is something you are doing or having a script/tool do over the host. Check out Excerpt from my Book on the subject of SCSI Reservation Conflicts and Operational concerns. Granted not everything can be done but in a perfect world. Chapter 5 of the book has more technical information about FC-SAN, etc. Hopefully this will explain the problem so that you can discover what is happening.
Note, not covered above, is that if you use an older version of VCB (version 1.0) then you will want to upgrade as that threw reservations like crazy.
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.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Are you using MSCS between a virtual a virtual machine and a physical machine?
no. this ESX has zero VM's on it right now.
Another thing for you to try would be to do a lun reset ( vmkfstools -L lunreset vmhba:0:1:6:0 ) here should be your vmhba that you having issues with.
Sorry bout the bad english. typing to slow with fast thoughts and also work 😛
Hope that helped.
Hello,
With 0 VMs, the culprit could be another ESX server or something else connected to the SAN. As Williamarrata stated you will want to find the LUN in question and try a reset. Have you added ANY agents to the system? Anything outside the normal VMware software stack? Also to what SAN are you attaching the device. I found that if you put more than 4 servers on an MSA1000 you will get SCSI Reservation conflicts. It depends on the SAN device or iSCSI device you are using to know if that will be the case. Also, is this BOOT from SAN? If so is there a VMFS on your Boot LUN?
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.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Edward, we are on the same path, right on.....I think mabey if you run "dmesg" and post it , lets see what it says.
Hope that helped.
ERIAL_PCI enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
floppy0: no floppy controllers found
RAMDISK driver initialized: 256 RAM disks of 96000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: ports already in use, skipping probe
hdc: HL-DT-STCD-RW/DVD DRIVE GCC-4244N, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: attached ide-cdrom driver.
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
libata version 1.20 loaded.
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 131072 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 7412k freed
VFS: Mounted root (ext2 filesystem).
Mod: 118: vmnix module init_module=0xe0811f88
VmkMsg: 282: Started vmkMsg thread.
HB: 253: hb timer on.
HB: 320: Started hb thread.
VMK: 194: STACK_TOP_LA=0xfd802ff0
VMK: 114: vmkmem[0] 0x20000 0x20000 0xbffca
VMK: 114: vmkmem[1] 0x20000 0x100000 0x43ffff
VMK: 114: vmkmem[2] 0x20000 0x0 0x0
VMK: 114: vmkmem[3] 0x20000 0x0 0x0
VMK: 114: vmkmem[4] 0x20000 0x0 0x0
VMK: 114: vmkmem[5] 0x20000 0x0 0x0
VMK: 114: vmkmem[6] 0x20000 0x0 0x0
VMK: 114: vmkmem[7] 0x20000 0x0 0x0
VMK: 114: vmkmem[8] 0x20000 0x0 0x0
VMK: 114: vmkmem[9] 0x20000 0x0 0x0
VMK: 114: vmkmem[10] 0x20000 0x0 0x0
VMK: 114: vmkmem[11] 0x20000 0x0 0x0
VMK: 114: vmkmem[12] 0x20000 0x0 0x0
VMK: 114: vmkmem[13] 0x20000 0x0 0x0
VMK: 114: vmkmem[14] 0x20000 0x0 0x0
VMK: 114: vmkmem[15] 0x20000 0x0 0x0
VMK: 114: vmkmem[16] 0x20000 0x0 0x0
VMK: 114: vmkmem[17] 0x20000 0x0 0x0
VMK: 114: vmkmem[18] 0x20000 0x0 0x0
VMK: 114: vmkmem[19] 0x20000 0x0 0x0
VMK: 114: vmkmem[20] 0x20000 0x0 0x0
VMK: 114: vmkmem[21] 0x20000 0x0 0x0
VMK: 114: vmkmem[22] 0x20000 0x0 0x0
VMK: 114: vmkmem[23] 0x20000 0x0 0x0
VMK: 114: vmkmem[24] 0x20000 0x0 0x0
VMK: 114: vmkmem[25] 0x20000 0x0 0x0
VMK: 114: vmkmem[26] 0x20000 0x0 0x0
VMK: 114: vmkmem[27] 0x20000 0x0 0x0
VMK: 114: vmkmem[28] 0x20000 0x0 0x0
VMK: 114: vmkmem[29] 0x20000 0x0 0x0
VMK: 114: vmkmem[30] 0x20000 0x0 0x0
VMK: 114: vmkmem[31] 0x20000 0x0 0x0
IRQ: 195: COS is using IOAPIC
WARNING: IRQ: 1240: 0:0.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:2.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:3.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:4.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:5.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:6.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:7.0 has interrupt pin 255
IRQ: 1261: Setting up 0:8.0-0 with irq 16
WARNING: IRQ: 1240: 0:16.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:16.1 has interrupt pin 255
WARNING: IRQ: 1240: 0:16.2 has interrupt pin 255
WARNING: IRQ: 1240: 0:17.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:19.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:21.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:22.0 has interrupt pin 255
IRQ: 1261: Setting up 0:28.0-0 with irq 0
IRQ: 1261: Setting up 0:28.1-1 with irq 0
IRQ: 1261: Setting up 0:29.0-0 with irq 21
IRQ: 1261: Setting up 0:29.1-1 with irq 20
IRQ: 1261: Setting up 0:29.2-2 with irq 21
IRQ: 1261: Setting up 0:29.3-3 with irq 20
IRQ: 1261: Setting up 0:29.7-0 with irq 21
WARNING: IRQ: 1240: 0:30.0 has interrupt pin 255
WARNING: IRQ: 1240: 0:31.0 has interrupt pin 255
IRQ: 1261: Setting up 0:31.2-1 with irq 19
IRQ: 1261: Setting up 0:31.3-1 with irq 19
WARNING: IRQ: 1240: 26:0.0 has interrupt pin 255
WARNING: IRQ: 1240: 26:0.3 has interrupt pin 255
WARNING: IRQ: 1240: 27:0.0 has interrupt pin 255
IRQ: 1261: Setting up 27:1.0-0 with irq 22
IRQ: 1261: Setting up 7:0.0-0 with irq 18
IRQ: 1261: Setting up 28:0.0-0 with irq 16
IRQ: 1261: Setting up 36:0.0-0 with irq 17
IRQ: 1261: Setting up 36:0.1-1 with irq 18
IRQ: 1261: Setting up 4:0.0-0 with irq 17
WARNING: IRQ: 1240: 2:0.0 has interrupt pin 255
WARNING: IRQ: 1240: 5:0.0 has interrupt pin 255
IRQ: 1261: Setting up 3:0.0-0 with irq 16
IRQ: 1261: Setting up 6:0.0-0 with irq 17
IRQ: 1261: Setting up 1:6.0-0 with irq 20
IRQ: 1271: Interrupt map: 0x2780800, len: 19
IRQ: 1276: vmnixIOApicInfo 0x1f8ae000, len 256
IRQ: 913: irq 0 is used
IRQ: 917: irq 0 is enabled
IRQ: 913: irq 1 is used
IRQ: 917: irq 1 is enabled
IRQ: 913: irq 2 is used
IRQ: 917: irq 2 is enabled
IRQ: 913: irq 15 is used
IRQ: 917: irq 15 is enabled
IRQ: 1101: Usurping irq 0 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 1 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 2 (from XT-PIC to vmnix-edge)
IRQ: 1101: Usurping irq 4 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 6 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 8 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 9 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 12 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 13 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 14 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 15 (from IO-APIC-edge to vmnix-edge)
IRQ: 1101: Usurping irq 16 (from IO-APIC-level to vmnix-level)
IRQ: 1101: Usurping irq 17 (from IO-APIC-level to vmnix-level)
IRQ: 1101: Usurping irq 18 (from IO-APIC-level to vmnix-level)
IRQ: 1101: Usurping irq 19 (from IO-APIC-level to vmnix-level)
IRQ: 1101: Usurping irq 20 (from IO-APIC-level to vmnix-level)
IRQ: 1101: Usurping irq 21 (from IO-APIC-level to vmnix-level)
VGA: 338: VGA start b8000 end c0000 mapped start c00b8000 char height 16
VGA: 442:
VGA: 470: 0
Console: switching to colour VMNIX-VGA 80x25
scsi0 : vsd
scsi1 : aacraid_esx30
Vendor: ServeRA Model: Drive 1 Rev: V1.0
Type: Direct-Access ANSI SCSI revision: 02
VMWARE SCSI Id: Supported VPD pages for sda : 0x1f 0x0
VMWARE SCSI Id: Could not get disk id for sda
:VMWARE: Unique Device attached as scsi disk sda at scsi1, channel 0, id 0, lun 0
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 143155200 512-byte hdwr sectors (73295 MB)
Partition check:
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
scsi2 : qla2300_707_vmw
scsi3 : qla2300_707_vmw
Vendor: IBM Model: 2145 Rev: 0000
Type: Direct-Access ANSI SCSI revision: 04
Vendor: IBM Model: 2145 Rev: 0000
Type: Direct-Access ANSI SCSI revision: 04
Vendor: IBM Model: 2145 Rev: 0000
Type: Direct-Access ANSI SCSI revision: 04
Vendor: IBM Model: 2145 Rev: 0000
Type: Direct-Access ANSI SCSI revision: 04
Vendor: IBM Model: 2145 Rev: 0000
Type: Direct-Access ANSI SCSI revision: 04
VMWARE SCSI Id: Supported VPD pages for sdb : 0x0 0x80 0x83
VMWARE SCSI Id: Device id info for sdb: 0x1 0x3 0x0 0x10 0x60 0x5 0x7 0x68 0x1 0x82 0x80 0x9b 0xe0 0x0 0x0 0x0 0x0 0x0 0xc 0xd2 0x1 0x14 0x0 0x4 0x2 0x0 0x1 0x0 0x1 0x15 0x0 0x4 0x0 0x0 0x0 0x1
VMWARE SCSI Id: Id for sdb 0x60 0x05 0x07 0x68 0x01 0x82 0x80 0x9b 0xe0 0x00 0x00 0x00 0x00 0x00 0x0c 0xd2 0x32 0x31 0x34 0x35 0x20 0x20
VMWARE: Unique Device attached as scsi disk sdb at scsi2, channel 0, id 0, lun 1
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 1
VMWARE SCSI Id: Supported VPD pages for sdc : 0x0 0x80 0x83
VMWARE SCSI Id: Device id info for sdc: 0x1 0x3 0x0 0x10 0x60 0x5 0x7 0x68 0x1 0x82 0x80 0x9b 0xe0 0x0 0x0 0x0 0x0 0x0 0xc 0xd3 0x1 0x14 0x0 0x4 0x2 0x0 0x1 0x0 0x1 0x15 0x0 0x4 0x0 0x0 0x0 0x1
VMWARE SCSI Id: Id for sdc 0x60 0x05 0x07 0x68 0x01 0x82 0x80 0x9b 0xe0 0x00 0x00 0x00 0x00 0x00 0x0c 0xd3 0x32 0x31 0x34 0x35 0x20 0x20
VMWARE: Unique Device attached as scsi disk sdc at scsi2, channel 0, id 0, lun 2
Attached scsi disk sdc at scsi2, channel 0, id 0, lun 2
VMWARE SCSI Id: Supported VPD pages for sdd : 0x0 0x80 0x83
VMWARE SCSI Id: Device id info for sdd: 0x1 0x3 0x0 0x10 0x60 0x5 0x7 0x68 0x1 0x82 0x80 0x9b 0xe0 0x0 0x0 0x0 0x0 0x0 0xc 0xd4 0x1 0x14 0x0 0x4 0x2 0x0 0x1 0x0 0x1 0x15 0x0 0x4 0x0 0x0 0x0 0x0
VMWARE SCSI Id: Id for sdd 0x60 0x05 0x07 0x68 0x01 0x82 0x80 0x9b 0xe0 0x00 0x00 0x00 0x00 0x00 0x0c 0xd4 0x32 0x31 0x34 0x35 0x20 0x20
VMWARE: Unique Device attached as scsi disk sdd at scsi2, channel 0, id 0, lun 3
Attached scsi disk sdd at scsi2, channel 0, id 0, lun 3
VMWARE SCSI Id: Supported VPD pages for sde : 0x0 0x80 0x83
VMWARE SCSI Id: Device id info for sde: 0x1 0x3 0x0 0x10 0x60 0x5 0x7 0x68 0x1 0x82 0x80 0x9b 0xe0 0x0 0x0 0x0 0x0 0x0 0xf 0xdf 0x1 0x14 0x0 0x4 0x2 0x0 0x1 0x0 0x1 0x15 0x0 0x4 0x0 0x0 0x0 0x0
VMWARE SCSI Id: Id for sde 0x60 0x05 0x07 0x68 0x01 0x82 0x80 0x9b 0xe0 0x00 0x00 0x00 0x00 0x00 0x0f 0xdf 0x32 0x31 0x34 0x35 0x20 0x20
VMWARE: Unique Device attached as scsi disk sde at scsi2, channel 0, id 0, lun 4
Attached scsi disk sde at scsi2, channel 0, id 0, lun 4
VMWARE SCSI Id: Supported VPD pages for sdf : 0x0 0x80 0x83
VMWARE SCSI Id: Device id info for sdf: 0x1 0x3 0x0 0x10 0x60 0x5 0x7 0x68 0x1 0x82 0x80 0x9b 0xe0 0x0 0x0 0x0 0x0 0x0 0xc 0xa1 0x1 0x14 0x0 0x4 0x2 0x0 0x0 0x0 0x1 0x15 0x0 0x4 0x0 0x0 0x0 0x1 0x1 0x10 0x0 0x10 0x60 0x5 0x7 0x68 0x1 0x82 0x80 0x9b 0xe0 0x0 0x0 0x0 0x0 0x0 0x0 0x11
VMWARE SCSI Id: Id for sdf 0x60 0x05 0x07 0x68 0x01 0x82 0x80 0x9b 0xe0 0x00 0x00 0x00 0x00 0x00 0x0c 0xa1 0x32 0x31 0x34 0x35 0x20 0x20
VMWARE: Unique Device attached as scsi disk sdf at scsi2, channel 0, id 1, lun 0
Attached scsi disk sdf at scsi2, channel 0, id 1, lun 0
SCSI device sdb: 1363148800 512-byte hdwr sectors (697932 MB)
sdb: sdb1
SCSI device sdc: 1363148800 512-byte hdwr sectors (697932 MB)
sdc: sdc1
SCSI device sdd: 1363148800 512-byte hdwr sectors (697932 MB)
sdd: sdd1
SCSI device sde: 1048576000 512-byte hdwr sectors (536871 MB)
sde: sde1
SCSI device sdf: 838860800 512-byte hdwr sectors (429497 MB)
sdf: sdf1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 376k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 17:39:44 Jan 3 2008
usb-uhci.c: High bandwidth mode enabled
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0x2200, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0x2600, IRQ 20
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0x2a00, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.3 to 64
usb-uhci.c: USB UHCI at I/O 0x2e00, IRQ 20
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Setting latency timer of device 00:1d.7 to 64
ehci-hcd 00:1d.7: PCI device 8086:268c (Intel Corp.)
ehci-hcd 00:1d.7: irq 21, pci mem e10ce000
usb.c: new USB bus registered, assigned bus number 5
ehci-hcd 00:1d.7: enabled 64bit PCI DMA
PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
PCI: 00:1d.7 PCI cache line size corrected to 128.
ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 8 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
hub.c: connect-debounce failed, port 1 disabled
Adding Swap: 554200k swap-space (priority -1)
hub.c: new USB device 00:1d.0-1, assigned address 2
input0: USB HID v1.10 Keyboard on usb1:2.0
input1: USB HID v1.10 Mouse on usb1:2.1
hub.c: new USB device 00:1d.2-1, assigned address 2
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
input2: USB HID v1.10 Keyboard on usb3:2.0
input3: USB HID v1.10 Mouse on usb3:2.1
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
microcode: No suitable data for cpu 0
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
qla2x00_set_info starts at address = e112c060
qla2x00_set_info starts at address = e112c060
qla2x00_set_info starts at address = e112c060
scsi_register_dev_mod starting finish
scsi_register_dev_mod done with finish
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (4096 buckets, 32768 max) - 308 bytes per conntrack
Intel(R) PRO/1000 Network Driver - version 7.3.15
Copyright (c) 1999-2006 Intel Corporation.
Intel(R) PRO/1000 Network Driver - version 7.3.15
Copyright (c) 1999-2006 Intel Corporation.
ipmi message handler version 39
IPMI System Interface driver version 39, KCS version 39, SMIC version 39, BT version 39
ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca8
IPMI kcs interface initialized
ipmi device interface version 39
ppdev: user-space parallel port driver
ppdev0: claim the port first
lp: driver loaded but no devices found
ppdev1: claim the port first
ppdev2: claim the port first
ppdev3: claim the port first
ppdev4: claim the port first
ppdev5: claim the port first
ppdev6: claim the port first
ppdev7: claim the port first
Intel(R) PRO/1000 Network Driver - version 7.3.15
Copyright (c) 1999-2006 Intel Corporation.
Intel(R) PRO/1000 Network Driver - version 7.3.15
Copyright (c) 1999-2006 Intel Corporation.
Intel(R) PRO/1000 Network Driver - version 7.3.15
Copyright (c) 1999-2006 Intel Corporation.
Intel(R) PRO/1000 Network Driver - version 7.3.15
Copyright (c) 1999-2006 Intel Corporation.
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,1,0) : RESERVATION CONFLICT
scsi2 (0,0,2) : RESERVATION CONFLICT
scsi2 (0,0,2) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,3) : RESERVATION CONFLICT
scsi2 (0,0,3) : RESERVATION CONFLICT
scsi2 (0,0,1) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,2) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,2) : RESERVATION CONFLICT
scsi2 (0,0,2) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
scsi2 (0,0,1) : RESERVATION CONFLICT
scsi2 (0,0,1) : RESERVATION CONFLICT
scsi2 (0,0,1) : RESERVATION CONFLICT
scsi2 (0,0,4) : RESERVATION CONFLICT
Hello,
And the answers to my questions?
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.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Have you added ANY agents to the system? NO
Anything outside the normal VMware software stack? NO
Also to what SAN are you attaching the device. muliple
Also, is this BOOT from SAN? NO
If so is there a VMFS on your Boot LUN? n/a
Hello,
For the device that is receiving the SCSI Reservations to which SAN is it being attached? This does matter btw. What resides on that LUN? VMs or ancillary files (like isos).
SCSI Reservations occur when the host has been asked to manipulate the VMFS metadata. Any time it tries to do that, it requests a reservation, this reservation when released tells the other ESX servers attached to the LUN to renew its local cache. So a Conflict implies that it is asking for the reservation and at that time could not get one. Also, unless in your log file there is an outright SCSI failure, the reservation eventually succeeded. You should look at all the ESX servers attached to that LUN and see if they are also getting reservation requests. If so you may have a fabric issue of some sort.
Generally you should only be concerned if you see outright failures, but too many reservation requests also could me you have a balancing problem, fabric problem, or operations problem.
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.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization