qla24xx_abort_command in /var/log/vmkernel

RyanWI · ‎03-03-2008

We've been building out our vmware 3.5 enviroment and I've been noticing a lot of these entries in my vmkernel log. I don't have any in the /var/log/vmkwarning. Can anyone tell me what these mean?

Here are the last 30 lines from my vmkernel:

Mar 2 08:38:31 utomad0p0031 vmkernel: 24:19:08:42.652 cpu5:1211)Uplink: 2495: Setting capabilities 0x0 for device vmnic9

Mar 2 08:43:22 utomad0p0031 vmkernel: 24:19:13:33.804 cpu6:1066)<6>qla24xx_abort_command(1): handle to abort=1319
Mar 2 08:43:25 utomad0p0031 vmkernel: 24:19:13:36.805 cpu6:1066)<6>qla24xx_abort_command(4): handle to abort=1959
Mar 2 08:43:26 utomad0p0031 vmkernel: 24:19:13:37.636 cpu6:1066)<6>qla24xx_abort_command(3): handle to abort=1117
Mar 2 09:31:38 utomad0p0031 vmkernel: 24:20:01:49.478 cpu6:1066)<6>qla24xx_abort_command(3): handle to abort=1824
Mar 2 09:31:38 utomad0p0031 vmkernel: 24:20:01:49.479 cpu6:1066)<6>qla24xx_abort_command(1): handle to abort=1847
Mar 2 09:31:43 utomad0p0031 vmkernel: 24:20:01:54.551 cpu6:1066)<6>qla24xx_abort_command(3): handle to abort=1848
Mar 2 09:31:43 utomad0p0031 vmkernel: 24:20:01:54.551 cpu6:1066)<6>qla24xx_abort_command(1): handle to abort=1850
Mar 2 09:31:44 utomad0p0031 vmkernel: 24:20:01:55.478 cpu6:1066)<6>qla24xx_abort_command(2): handle to abort=385

Mar 2 09:31:45 utomad0p0031 vmkernel: 24:20:01:56.852 cpu7:1162)VSCSIFs: 439: fd 4210 status Busy

Mar 2 09:31:45 utomad0p0031 vmkernel: 24:20:01:56.864 cpu7:1162)VSCSIFs: 439: fd 4210 status Busy

Mar 2 09:31:45 utomad0p0031 vmkernel: 24:20:01:56.921 cpu3:1177)VSCSIFs: 439: fd 4223 status Busy

Mar 2 09:31:45 utomad0p0031 vmkernel: 24:20:01:57.050 cpu7:1162)VSCSIFs: 439: fd 4210 status Busy

Mar 2 09:31:45 utomad0p0031 vmkernel: 24:20:01:57.119 cpu6:1167)VSCSIFs: 439: fd 4215 status Busy

Mar 2 09:31:45 utomad0p0031 vmkernel: 24:20:01:57.217 cpu3:1182)VSCSIFs: 439: fd 4228 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.316 cpu6:1162)VSCSIFs: 439: fd 4210 status Busy

Mar 2 09:31:46 utomad0p0031 last message repeated 3 times

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.327 cpu3:1177)VSCSIFs: 439: fd 4223 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.391 cpu2:1182)VSCSIFs: 439: fd 4228 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.395 cpu6:1162)VSCSIFs: 439: fd 4210 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.468 cpu3:1177)VSCSIFs: 439: fd 4223 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.562 cpu3:1182)VSCSIFs: 439: fd 4228 status Busy

Mar 2 09:31:46 utomad0p0031 last message repeated 4 times

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.817 cpu6:1167)VSCSIFs: 439: fd 4215 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:57.883 cpu1:1172)VSCSIFs: 439: fd 4219 status Busy

Mar 2 09:31:46 utomad0p0031 vmkernel: 24:20:01:58.014 cpu2:1043)FS3: 4828: Reclaimed timed out heartbeat http://HB state abcdef02 offset 3846144 gen 3019 stamp 2145714621514 uuid 47aa0abf-5a08606f-75f1-00151757f609 jrnl drv 4.31

Mar 2 11:35:06 utomad0p0031 vmkernel: 24:22:05:18.156 cpu6:1066)<6>qla24xx_abort_command(3): handle to abort=707
Mar 2 11:35:06 utomad0p0031 vmkernel: 24:22:05:18.157 cpu7:1066)<6>qla24xx_abort_command(2): handle to abort=1095
Mar 2 12:21:04 utomad0p0031 vmkernel: 24:22:51:15.668 cpu7:1066)<6>qla24xx_abort_command(4): handle to abort=1583

bulldude · ‎06-20-2008

I saw the same vmkernel logs recently. It was with an EVA4400 SAN (fixed path policy - default). All paths were zoned and visible from both the ESX hosts and the SAN switches. Fixed by removing and reinserting the fiber cable. Until the cable was unplugged and reinserted the VMs on the LUN had very poor disk I/O performance on the path. I located the path by moving VMs of the host and then moving the active path between paths and using a test VM to generate disk I/O.

Did you resolve your issue?

Bucketenator · ‎04-29-2009

RyanWI,

Did you get to the bottom of this? We're seeing the same sort of issue on an EVA4400 ...

Thanks,

Bucket