Quantcast
Channel: VMware Communities : All Content - VMware ESXi 5
Viewing all articles
Browse latest Browse all 18761

Problem with LSI 9260-4i after upgrade ESXi from 5.0 to 5.1.0a

$
0
0

I installed on ESXi 5.0 offline bundle 5.1, and after this installed offline bundle 5.1.0а. Now, I have ~ # vmware -v
VMware ESXi 5.1.0 build-838463.

And in my log watching interesting situation /var/log/vmkernel.log

 

2012-11-28T10:05:42.290Z cpu7:5039)WARNING: ScsiDeviceIO: 1211: Device  naa.600605b0049021e017579dc7047fff41 performance has deteriorated. I/O  latency increased from average value of 19209 microseconds to 577155  microseconds.
2012-11-28T10:05:44.296Z cpu11:4107)WARNING:  ScsiDeviceIO: 1211: Device naa.600605b0049021e017579dc7047fff41  performance has deteriorated. I/O latency increased from average value  of 19264 microseconds to 580562 microseconds.
2012-11-28T10:05:51.541Z  cpu3:37757)WARNING: ScsiDeviceIO: 1211: Device  naa.600605b0049021e017579dc7047fff41 performance has deteriorated. I/O  latency increased from average value of 19406 microseconds to 602629  microseconds.
2012-11-28T10:06:39.775Z cpu9:6338)WARNING:  ScsiDeviceIO: 1211: Device naa.600605b0049021e017579dc7047fff41  performance has deteriorated. I/O latency increased from average value  of 20438 microseconds to 618588 microseconds.
2012-11-28T10:06:50.950Z  cpu0:6338)WARNING: ScsiDeviceIO: 1211: Device  naa.600605b0049021e017579dc7047fff41 performance has deteriorated. I/O  latency increased from average value of 20666 microseconds to 743760  microseconds.
2012-11-28T10:07:31.248Z cpu9:6339)ScsiDeviceIO: 1191:  Device naa.600605b0049021e017579dc7047fff41 performance has improved.  I/O latency reduced from 743760 microseconds to 145638 microseconds.
2012-11-28T10:07:31.930Z  cpu9:37983)VSCSI: 2370: handle 8198(vscsi0:0):Reset request on FSS  handle 5188905 (67 outstanding commands)
2012-11-28T10:07:31.930Z cpu0:4202)VSCSI: 2648: handle 8198(vscsi0:0):Reset [Retries: 0/0]                       
2012-11-28T10:07:31.930Z cpu0:4202)megasas: ABORT sn 1436974 cmd=0x8a retries=0 tmo=0                            
2012-11-28T10:07:31.930Z cpu0:4202)<5>0 :: megasas: RESET -1436974 cmd=8a retries=0                              
2012-11-28T10:07:31.930Z cpu0:4202)megaraid_sas: HBA reset handler invoked without an internal reset condition.
2012-11-28T10:07:31.994Z  cpu1:4097)WARNING: LinScsi: SCSILinuxQueueCommand:1193:queuecommand  failed with status = 0x1055 Host Busy vmhba1:2:0:0 (driver name: LSI  Logic SAS based MegaRAID driver) - Message repeated 1 time
2012-11-28T10:07:31.994Z  cpu1:4097)ScsiDeviceIO: 2303: Cmd(0x412400735100) 0x2a, CmdSN  0x800201a0 from world 6336 to dev "naa.600605b0049021e017579dc7047fff41"  failed H:0x0 D:0x8 P:0x0 Possible sense data: 0x0 0x0 0x0.
2012-11-28T10:07:32.017Z  cpu1:6335)ScsiDeviceIO: 2303: Cmd(0x41240077cd40) 0x2a, CmdSN 0x5542  from world 4173 to dev "naa.600605b0049021e017579dc7047fff41" failed  H:0x0 D:0x8 P:0x0 Possible sense data: 0x0 0x0 0x0.
2012-11-28T10:07:32.941Z  cpu0:4202)<7>megaraid_sas: megasas_wait_for_outstanding: line  2156: AFTER HBA reset handler invoked without an internal reset  condition:   took 1 seconds. Max is 180.
2012-11-28T10:07:32.941Z cpu0:4202)megaraid_sas: no more pending commands remain after reset handling.
2012-11-28T10:07:32.941Z cpu0:4202)<5>megasas: reset successful                                                      
                                                                                                                     
2012-11-28T10:07:32.941Z cpu0:4202)megasas: ABORT sn 1436980 cmd=0x2a retries=0 tmo=0                                
2012-11-28T10:07:32.941Z cpu0:4202)<5>0 :: megasas: RESET -1436980 cmd=2a retries=0                                  
2012-11-28T10:07:32.942Z cpu0:4202)megaraid_sas: HBA reset handler invoked without an internal reset condition.
2012-11-28T10:07:32.942Z  cpu0:4202)<7>megaraid_sas: megasas_wait_for_outstanding: line  2156: AFTER HBA reset handler invoked without an internal reset  condition:   took 0 seconds. Max is 180.
2012-11-28T10:07:32.942Z cpu0:4202)megaraid_sas: no more pending commands remain after reset handling.               
2012-11-28T10:07:32.942Z cpu0:4202)<5>megasas: reset successful                                                      
                                                                                                                     
2012-11-28T10:07:32.942Z cpu0:4202)megasas: ABORT sn 1437298 cmd=0x8a retries=0 tmo=0
2012-11-28T10:07:32.942Z cpu0:4202)<5>0 :: megasas: RESET -1437298 cmd=8a retries=0                                  
2012-11-28T10:07:32.942Z cpu0:4202)megaraid_sas: HBA reset handler invoked without an internal reset condition.      
2012-11-28T10:07:32.942Z  cpu0:4202)<7>megaraid_sas: megasas_wait_for_outstanding: line  2156: AFTER HBA reset handler invoked without an internal reset  condition:   took 0 seconds. Max is 180.
2012-11-28T10:07:32.942Z cpu0:4202)megaraid_sas: no more pending commands remain after reset handling.               
2012-11-28T10:07:32.942Z cpu0:4202)<5>megasas: reset successful

 

Now periodically latensi disk subsystem rolls over to the upper grades, respectively guest VMs very slow. I suspect that the problem is in the new drivers of raid controller, tell where to dig?


Viewing all articles
Browse latest Browse all 18761

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>