VMware Cloud Community
jonneybegood
Contributor
Contributor

Disk reservation /contension after adding 2TB LUN

Hi-

I recently created a 2TB LUN on the SAN for an Exchange mail store. Since creating the LUN and migrating the Exchange LUN into it our ESX servers are doing allot of complaining about disk reservations and contention. The result is all servers / VM’s attached to the SAN have tanked in their performance by 50+%

Has anybody else experienced this and what was done to correct it? I’ve gotten the run around from VMWare and EMC for the past week each blaming the other.

Below is what we see in putty

vmkernel
Mar 22 21:43:13 XXX-XXX-ESX-01 vmkernel: 0:08:11:00.448 cpu2:4292)ScsiDeviceIO: 770: Command 0x3c to device "naa.600601600b12200008ae8adbe5e0de11" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
Mar 22 21:43:13 XXX-XXX-ESX-01 vmkernel: 0:08:11:00.449 cpu2:4292)NMP: nmp_CompleteCommandForPath: Command 0x3c (0x41000511db80) to NMP device "naa.600601600b12200008ae8adbe5e0de11" failed on physical path "vmhba1:C0:T0:L25" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
vmkwarning
Mar 22 21:05:11 XXX-XXX-ESX-01 vmkernel: 0:07:32:58.381 cpu2:4105)WARNING: Partition: 705: Partition table read from device mpx.vmhba0:C0:T0:L0 failed: Not supported
Mar 22 21:05:46 XXX-XXX-ESX-01 vmkernel: 0:07:33:33.475 cpu2:4107)WARNING: LinBlock: LinuxBlockCommand: READ(10) past end of device on major 104 - 0 + 1 > 0

Tags (3)
0 Kudos
1 Reply
idle-jam
Immortal
Immortal

Maximum detected LUN is only 2TB-512KB. Anything more than that would have weird effect. i would suggest you creating a bit smaller LUN or 1TB x 2.

0 Kudos