- VMware Technology Network
- :
- Cloud & SDDC
- :
- VI 3.X
- :
- VI: VMware ESX™ 3.5 Discussions
- :
- SCSI Issues and timeouts
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Can someone please help me with the error messages I have been getting in my vmkernel log, this is one host from an eight host HA Cluster with only one VM in the cluster at present:
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.030 cpu1:1028)SCSI: 3753: AsyncIO timeout (5000); aborting cmd w/ sn 62, handle 1af2/0x6a01618
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.030 cpu1:1028)LinSCSI: 3596: Aborting cmds with world 1024, originHandle 0x6a01618, originSN 62 from vmhba0:0:2
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.031 cpu1:1028)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.031 cpu1:1028)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
Apr 30 21:05:42 servername vmkernel: 0:07:27:22.036 cpu1:1028)SCSI: 3753: AsyncIO timeout (5000); aborting cmd w/ sn 63, handle 1af2/0x6a01618
Apr 30 21:05:42 servername vmkernel: 0:07:27:22.036 cpu1:1028)LinSCSI: 3596: Aborting cmds with world 1024, originHandle 0x6a01618, originSN 63 from vmhba0:0:2
Apr 30 21:05:42 servername vmkernel: 0:07:27:22.037 cpu1:1028)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
Apr 30 21:05:42 servername vmkernel: 0:07:27:22.037 cpu1:1028)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
Apr 30 21:05:43 servername vmkernel: 0:07:27:23.149 cpu2:1030)FS3: 4280: Waiting for timed-out heartbeat \[HB state abcdef02 offset 3554816 gen 385 stamp 26842107857 uuid 4635d55e-0cd64185-0705-001a4bd15486 jrnl scsi(0): Port database changed.
May 1 01:24:06 servername vmkernel: 0:11:45:46.563 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:24:06 servername vmkernel: 0:11:45:46.563 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:24:06 servername vmkernel: 0:11:45:46.563 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:24:06 servername vmkernel: 0:11:45:46.563 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:24:07 servername vmkernel: 0:11:45:46.763 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:24:07 servername vmkernel: 0:11:45:46.763 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:24:07 servername vmkernel: 0:11:45:46.763 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:24:07 servername vmkernel: 0:11:45:46.763 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:24:07 servername vmkernel: 0:11:45:47.063 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:24:07 servername vmkernel: 0:11:45:47.063 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:24:07 servername vmkernel: 0:11:45:47.231 cpu2:1034)SCSI: 8043: vmhba0:0:2:0 status = 2/0 0x6 0x29 0x0
May 1 01:24:07 servername vmkernel: 0:11:45:47.231 cpu2:1034)SCSI: 8074: vmhba0:0:2:0 Retry (unit attn)
May 1 01:24:07 servername vmkernel: 0:11:45:47.364 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:24:07 servername vmkernel: 0:11:45:47.364 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:24:07 servername vmkernel: 0:11:45:47.364 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:24:07 servername vmkernel: 0:11:45:47.364 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:24:08 servername vmkernel: 0:11:45:47.615 cpu2:1034)SCSI: 8043: vmhba0:0:3:0 status = 2/0 0x6 0x29 0x0
May 1 01:24:08 servername vmkernel: 0:11:45:47.615 cpu2:1034)SCSI: 8074: vmhba0:0:3:0 Retry (unit attn)
May 1 01:24:08 servername vmkernel: 0:11:45:48.030 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic0 cmd=0x8946 ifr=cd34beb4 status=0x2bacffa1
May 1 01:24:08 servername vmkernel: 0:11:45:48.201 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic2 cmd=0x8946 ifr=cd34beb4 status=0x2bacffa1
May 1 01:24:10 servername vmkernel: 0:11:45:50.312 cpu1:1040)SCSI: 8074: vmhba0:0:1:0 Retry (unit attn)
May 1 01:24:10 servername last message repeated 2 times
May 1 01:24:10 servername vmkernel: 0:11:45:50.313 cpu1:1040)SCSI: 8074: vmhba0:0:2:0 Retry (unit attn)
May 1 01:24:10 servername last message repeated 2 times
May 1 01:24:10 servername vmkernel: 0:11:45:50.314 cpu1:1040)SCSI: 8074: vmhba0:0:3:0 Retry (unit attn)
May 1 01:24:10 servername last message repeated 2 times
May 1 01:24:10 servername vmkernel: 0:11:45:50.314 cpu1:1040)SCSI: 8074: vmhba1:5:1:0 Retry (unit attn)
May 1 01:24:10 servername vmkernel: 0:11:45:50.314 cpu1:1040)SCSI: 8074: vmhba1:5:1:0 Retry (unit attn)
May 1 01:24:10 servername vmkernel: 0:11:45:50.315 cpu1:1040)SCSI: 8074: vmhba1:5:2:0 Retry (unit attn)
May 1 01:24:10 servername vmkernel: 0:11:45:50.315 cpu1:1040)SCSI: 8074: vmhba1:5:2:0 Retry (unit attn)
May 1 01:34:19 servername vmkernel: 0:11:55:59.000 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:34:19 servername vmkernel: 0:11:55:59.000 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:34:19 servername vmkernel: 0:11:55:59.000 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:34:19 servername vmkernel: 0:11:55:59.000 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:34:19 servername vmkernel: 0:11:55:59.502 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:34:19 servername vmkernel: 0:11:55:59.502 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:34:19 servername vmkernel: 0:11:55:59.502 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:34:19 servername vmkernel: 0:11:55:59.502 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:34:20 servername vmkernel: 0:11:56:00.002 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:34:20 servername vmkernel: 0:11:56:00.002 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:34:20 servername vmkernel: 0:11:56:00.203 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:34:20 servername vmkernel: 0:11:56:00.203 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:34:21 servername vmkernel: 0:11:56:01.026 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic0 cmd=0x8946 ifr=c23f7eb4 status=0x2bacffa1
May 1 01:39:26 servername vmkernel: 0:12:01:06.225 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:26 servername vmkernel: 0:12:01:06.225 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:26 servername vmkernel: 0:12:01:06.225 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:39:26 servername vmkernel: 0:12:01:06.225 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:39:26 servername vmkernel: 0:12:01:06.425 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:26 servername vmkernel: 0:12:01:06.425 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:26 servername vmkernel: 0:12:01:06.425 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:39:26 servername vmkernel: 0:12:01:06.425 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:39:27 servername vmkernel: 0:12:01:06.625 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:27 servername vmkernel: 0:12:01:06.625 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:27 servername vmkernel: 0:12:01:06.625 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:39:27 servername vmkernel: 0:12:01:06.625 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:39:27 servername vmkernel: 0:12:01:06.925 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:27 servername vmkernel: 0:12:01:06.925 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:27 servername vmkernel: 0:12:01:07.125 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:27 servername vmkernel: 0:12:01:07.125 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:27 servername vmkernel: 0:12:01:07.126 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:39:27 servername vmkernel: 0:12:01:07.126 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:39:27 servername vmkernel: 0:12:01:07.326 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:27 servername vmkernel: 0:12:01:07.326 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:27 servername vmkernel: 0:12:01:07.326 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:39:27 servername vmkernel: 0:12:01:07.326 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:39:28 servername vmkernel: 0:12:01:07.827 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:28 servername vmkernel: 0:12:01:07.827 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:39:28 servername vmkernel: 0:12:01:07.827 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:39:28 servername vmkernel: 0:12:01:07.827 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:39:28 servername vmkernel: 0:12:01:08.228 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:39:28 servername vmkernel: 0:12:01:08.228 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:33 servername vmkernel: 0:12:06:13.550 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:33 servername vmkernel: 0:12:06:13.550 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:33 servername vmkernel: 0:12:06:13.550 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:33 servername vmkernel: 0:12:06:13.550 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:34 servername vmkernel: 0:12:06:13.750 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:34 servername vmkernel: 0:12:06:13.750 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:34 servername vmkernel: 0:12:06:13.750 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:34 servername vmkernel: 0:12:06:13.750 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:34 servername vmkernel: 0:12:06:13.950 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:34 servername vmkernel: 0:12:06:13.950 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:34 servername vmkernel: 0:12:06:13.950 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:34 servername vmkernel: 0:12:06:13.950 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:34 servername vmkernel: 0:12:06:14.150 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:34 servername vmkernel: 0:12:06:14.150 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:34 servername vmkernel: 0:12:06:14.150 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:34 servername vmkernel: 0:12:06:14.150 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:34 servername vmkernel: 0:12:06:14.350 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:34 servername vmkernel: 0:12:06:14.350 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:34 servername vmkernel: 0:12:06:14.350 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:34 servername vmkernel: 0:12:06:14.350 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:34 servername vmkernel: 0:12:06:14.550 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:34 servername vmkernel: 0:12:06:14.550 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:34 servername vmkernel: 0:12:06:14.550 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:34 servername vmkernel: 0:12:06:14.550 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:35 servername vmkernel: 0:12:06:14.750 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:35 servername vmkernel: 0:12:06:14.750 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:35 servername vmkernel: 0:12:06:14.750 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:35 servername vmkernel: 0:12:06:14.750 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:35 servername vmkernel: 0:12:06:14.950 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:35 servername vmkernel: 0:12:06:14.950 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:35 servername vmkernel: 0:12:06:14.950 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:35 servername vmkernel: 0:12:06:14.950 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:35 servername vmkernel: 0:12:06:15.151 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:35 servername vmkernel: 0:12:06:15.151 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:35 servername vmkernel: 0:12:06:15.151 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:35 servername vmkernel: 0:12:06:15.151 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:35 servername vmkernel: 0:12:06:15.351 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:35 servername vmkernel: 0:12:06:15.351 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:35 servername vmkernel: 0:12:06:15.351 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:35 servername vmkernel: 0:12:06:15.351 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:35 servername vmkernel: 0:12:06:15.551 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:35 servername vmkernel: 0:12:06:15.551 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:35 servername vmkernel: 0:12:06:15.551 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:35 servername vmkernel: 0:12:06:15.551 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:36 servername vmkernel: 0:12:06:15.751 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:36 servername vmkernel: 0:12:06:15.751 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:36 servername vmkernel: 0:12:06:15.751 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:36 servername vmkernel: 0:12:06:15.751 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:36 servername vmkernel: 0:12:06:15.951 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:36 servername vmkernel: 0:12:06:15.951 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:36 servername vmkernel: 0:12:06:15.951 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:36 servername vmkernel: 0:12:06:15.951 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:36 servername vmkernel: 0:12:06:16.151 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:36 servername vmkernel: 0:12:06:16.151 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:36 servername vmkernel: 0:12:06:16.151 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:36 servername vmkernel: 0:12:06:16.151 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:36 servername vmkernel: 0:12:06:16.351 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:36 servername vmkernel: 0:12:06:16.351 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:36 servername vmkernel: 0:12:06:16.351 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:36 servername vmkernel: 0:12:06:16.351 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:36 servername vmkernel: 0:12:06:16.551 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:36 servername vmkernel: 0:12:06:16.551 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:36 servername vmkernel: 0:12:06:16.551 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:36 servername vmkernel: 0:12:06:16.551 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:37 servername vmkernel: 0:12:06:16.751 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:37 servername vmkernel: 0:12:06:16.751 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:37 servername vmkernel: 0:12:06:16.751 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:37 servername vmkernel: 0:12:06:16.751 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:37 servername vmkernel: 0:12:06:16.951 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:37 servername vmkernel: 0:12:06:16.951 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:37 servername vmkernel: 0:12:06:16.951 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:37 servername vmkernel: 0:12:06:16.951 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:37 servername vmkernel: 0:12:06:17.152 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:37 servername vmkernel: 0:12:06:17.152 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:37 servername vmkernel: 0:12:06:17.152 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:37 servername vmkernel: 0:12:06:17.152 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:37 servername vmkernel: 0:12:06:17.352 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:37 servername vmkernel: 0:12:06:17.352 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:37 servername vmkernel: 0:12:06:17.352 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:37 servername vmkernel: 0:12:06:17.352 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:37 servername vmkernel: 0:12:06:17.552 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:37 servername vmkernel: 0:12:06:17.552 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:37 servername vmkernel: 0:12:06:17.552 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:37 servername vmkernel: 0:12:06:17.552 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:38 servername vmkernel: 0:12:06:17.752 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:38 servername vmkernel: 0:12:06:17.752 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:38 servername vmkernel: 0:12:06:17.752 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:38 servername vmkernel: 0:12:06:17.752 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:38 servername vmkernel: 0:12:06:17.952 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:38 servername vmkernel: 0:12:06:17.952 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:38 servername vmkernel: 0:12:06:17.952 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:38 servername vmkernel: 0:12:06:17.952 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:38 servername vmkernel: 0:12:06:18.152 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:38 servername vmkernel: 0:12:06:18.152 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:38 servername vmkernel: 0:12:06:18.152 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:38 servername vmkernel: 0:12:06:18.152 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:38 servername vmkernel: 0:12:06:18.352 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:38 servername vmkernel: 0:12:06:18.352 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:38 servername vmkernel: 0:12:06:18.552 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:38 servername vmkernel: 0:12:06:18.552 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:38 servername vmkernel: 0:12:06:18.552 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:38 servername vmkernel: 0:12:06:18.552 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:39 servername vmkernel: 0:12:06:18.752 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:18.752 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:18.752 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:39 servername vmkernel: 0:12:06:18.752 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:39 servername vmkernel: 0:12:06:18.952 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:18.952 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:18.952 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:18.952 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:18.952 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:39 servername vmkernel: 0:12:06:18.952 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:39 servername vmkernel: 0:12:06:19.152 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:19.152 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:19.152 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:19.153 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:19.153 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:19.153 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:19.153 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:39 servername vmkernel: 0:12:06:19.153 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:39 servername vmkernel: 0:12:06:19.353 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:19.353 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:19.353 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:19.353 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:19.353 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:39 servername vmkernel: 0:12:06:19.353 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:39 servername vmkernel: 0:12:06:19.553 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:39 servername vmkernel: 0:12:06:19.553 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:39 servername vmkernel: 0:12:06:19.553 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:39 servername vmkernel: 0:12:06:19.553 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:40 servername vmkernel: 0:12:06:19.753 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:19.753 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:19.753 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:40 servername vmkernel: 0:12:06:19.753 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:40 servername vmkernel: 0:12:06:19.953 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:40 servername vmkernel: 0:12:06:20.153 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:20.153 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:20.153 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:40 servername vmkernel: 0:12:06:20.153 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:40 servername vmkernel: 0:12:06:20.353 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:20.353 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:20.353 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:20.353 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:20.353 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:40 servername vmkernel: 0:12:06:20.353 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:40 servername vmkernel: 0:12:06:20.553 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:40 servername vmkernel: 0:12:06:20.554 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:40 servername vmkernel: 0:12:06:20.554 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:40 servername vmkernel: 0:12:06:20.554 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:41 servername vmkernel: 0:12:06:20.754 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:41 servername vmkernel: 0:12:06:20.954 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:20.954 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:20.954 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:20.954 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:20.954 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:41 servername vmkernel: 0:12:06:20.954 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:41 servername vmkernel: 0:12:06:21.154 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:21.154 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:21.154 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:21.154 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:21.154 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:41 servername vmkernel: 0:12:06:21.154 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:41 servername vmkernel: 0:12:06:21.354 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:41 servername vmkernel: 0:12:06:21.554 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:41 servername vmkernel: 0:12:06:21.554 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:41 servername vmkernel: 0:12:06:21.554 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:41 servername vmkernel: 0:12:06:21.554 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:42 servername vmkernel: 0:12:06:21.754 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:21.754 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:21.754 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:21.754 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:21.754 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:42 servername vmkernel: 0:12:06:21.754 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:42 servername vmkernel: 0:12:06:21.954 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:21.954 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:21.954 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:42 servername vmkernel: 0:12:06:21.954 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:42 servername vmkernel: 0:12:06:22.154 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:22.154 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:22.154 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:42 servername vmkernel: 0:12:06:22.154 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:42 servername vmkernel: 0:12:06:22.354 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:22.354 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:22.354 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:22.354 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:22.354 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:42 servername vmkernel: 0:12:06:22.354 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:42 servername vmkernel: 0:12:06:22.554 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:42 servername vmkernel: 0:12:06:22.554 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:42 servername vmkernel: 0:12:06:22.554 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:42 servername vmkernel: 0:12:06:22.554 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:43 servername vmkernel: 0:12:06:22.744 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:43 servername vmkernel: 0:12:06:22.744 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:43 servername vmkernel: 0:12:06:22.744 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:43 servername vmkernel: 0:12:06:22.744 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:43 servername vmkernel: 0:12:06:22.944 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:43 servername vmkernel: 0:12:06:22.944 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:43 servername vmkernel: 0:12:06:22.944 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:43 servername vmkernel: 0:12:06:22.944 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:43 servername vmkernel: 0:12:06:23.144 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:43 servername vmkernel: 0:12:06:23.144 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:43 servername vmkernel: 0:12:06:23.144 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:43 servername vmkernel: 0:12:06:23.144 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:43 servername vmkernel: 0:12:06:23.344 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:43 servername vmkernel: 0:12:06:23.344 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:23.544 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:23.544 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:23.544 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:23.544 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:23.544 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:44 servername vmkernel: 0:12:06:23.544 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:44 servername vmkernel: 0:12:06:23.744 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:23.744 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:23.744 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:23.744 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:23.744 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:44 servername vmkernel: 0:12:06:23.744 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:44 servername vmkernel: 0:12:06:23.944 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:23.944 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:23.944 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:44 servername vmkernel: 0:12:06:23.944 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:44 servername vmkernel: 0:12:06:24.144 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:24.144 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:24.144 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:24.144 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:24.144 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:44 servername vmkernel: 0:12:06:24.144 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:44 servername vmkernel: 0:12:06:24.344 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:24.344 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:24.345 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:24.345 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:24.345 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:44 servername vmkernel: 0:12:06:24.345 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:44 servername vmkernel: 0:12:06:24.545 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:44 servername vmkernel: 0:12:06:24.545 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:44 servername vmkernel: 0:12:06:24.545 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:44 servername vmkernel: 0:12:06:24.545 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:45 servername vmkernel: 0:12:06:24.745 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:24.745 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:24.745 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:45 servername vmkernel: 0:12:06:24.745 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:45 servername vmkernel: 0:12:06:24.945 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:24.945 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:24.945 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:24.945 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:24.945 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:45 servername vmkernel: 0:12:06:24.945 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:45 servername vmkernel: 0:12:06:25.145 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:45 servername vmkernel: 0:12:06:25.345 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:25.345 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:25.345 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:25.345 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:25.345 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:45 servername vmkernel: 0:12:06:25.345 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:45 servername vmkernel: 0:12:06:25.545 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:45 servername vmkernel: 0:12:06:25.545 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:45 servername vmkernel: 0:12:06:25.545 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:45 servername vmkernel: 0:12:06:25.545 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:46 servername vmkernel: 0:12:06:25.745 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:46 servername vmkernel: 0:12:06:25.745 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:46 servername vmkernel: 0:12:06:25.745 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:46 servername vmkernel: 0:12:06:25.745 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:46 servername vmkernel: 0:12:06:25.945 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:46 servername vmkernel: 0:12:06:25.945 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:46 servername vmkernel: 0:12:06:25.945 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:46 servername vmkernel: 0:12:06:25.945 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:46 servername vmkernel: 0:12:06:26.145 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:46 servername vmkernel: 0:12:06:26.145 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:46 servername vmkernel: 0:12:06:26.145 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:46 servername vmkernel: 0:12:06:26.145 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:46 servername vmkernel: 0:12:06:26.345 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:46 servername vmkernel: 0:12:06:26.345 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:46 servername vmkernel: 0:12:06:26.345 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:46 servername vmkernel: 0:12:06:26.345 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:46 servername vmkernel: 0:12:06:26.546 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:46 servername vmkernel: 0:12:06:26.546 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:46 servername vmkernel: 0:12:06:26.546 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:46 servername vmkernel: 0:12:06:26.546 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:47 servername vmkernel: 0:12:06:26.746 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:26.746 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:26.746 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:26.746 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:26.746 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:47 servername vmkernel: 0:12:06:26.746 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:47 servername vmkernel: 0:12:06:26.946 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:26.946 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:26.946 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:26.946 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:26.946 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:47 servername vmkernel: 0:12:06:26.946 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:47 servername vmkernel: 0:12:06:27.146 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:27.146 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:27.146 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:47 servername vmkernel: 0:12:06:27.146 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:47 servername vmkernel: 0:12:06:27.346 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:27.346 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:27.346 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:47 servername vmkernel: 0:12:06:27.346 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:47 servername vmkernel: 0:12:06:27.546 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:47 servername vmkernel: 0:12:06:27.546 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:47 servername vmkernel: 0:12:06:27.546 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:47 servername vmkernel: 0:12:06:27.546 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:48 servername vmkernel: 0:12:06:27.746 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:27.746 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:27.746 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:48 servername vmkernel: 0:12:06:27.746 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:48 servername vmkernel: 0:12:06:27.946 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:27.946 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:27.946 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:27.946 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:27.946 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:48 servername vmkernel: 0:12:06:27.946 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:48 servername vmkernel: 0:12:06:28.146 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:28.146 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:28.147 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:28.147 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:28.147 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:48 servername vmkernel: 0:12:06:28.147 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:48 servername vmkernel: 0:12:06:28.347 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:28.347 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:28.347 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:48 servername vmkernel: 0:12:06:28.347 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:48 servername vmkernel: 0:12:06:28.547 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:48 servername vmkernel: 0:12:06:28.547 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:48 servername vmkernel: 0:12:06:28.547 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:48 servername vmkernel: 0:12:06:28.547 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:49 servername vmkernel: 0:12:06:28.747 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:49 servername vmkernel: 0:12:06:28.747 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:49 servername vmkernel: 0:12:06:28.747 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:49 servername vmkernel: 0:12:06:28.747 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:49 servername vmkernel: 0:12:06:28.947 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:49 servername vmkernel: 0:12:06:28.947 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:49 servername vmkernel: 0:12:06:28.947 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:49 servername vmkernel: 0:12:06:28.947 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:49 servername vmkernel: 0:12:06:28.947 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:49 servername vmkernel: 0:12:06:28.947 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:49 servername vmkernel: 0:12:06:29.147 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:49 servername vmkernel: 0:12:06:29.147 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:49 servername vmkernel: 0:12:06:29.147 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:49 servername vmkernel: 0:12:06:29.147 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:49 servername vmkernel: 0:12:06:29.347 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:49 servername vmkernel: 0:12:06:29.347 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:49 servername vmkernel: 0:12:06:29.347 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:49 servername vmkernel: 0:12:06:29.347 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:50 servername vmkernel: 0:12:06:29.647 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:50 servername vmkernel: 0:12:06:29.647 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:50 servername vmkernel: 0:12:06:29.847 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:50 servername vmkernel: 0:12:06:29.847 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:50 servername vmkernel: 0:12:06:29.847 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:50 servername vmkernel: 0:12:06:29.847 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:50 servername vmkernel: 0:12:06:30.047 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:50 servername vmkernel: 0:12:06:30.047 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:50 servername vmkernel: 0:12:06:30.047 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:50 servername vmkernel: 0:12:06:30.047 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:50 servername vmkernel: 0:12:06:30.248 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:50 servername vmkernel: 0:12:06:30.248 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:50 servername vmkernel: 0:12:06:30.248 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:50 servername vmkernel: 0:12:06:30.248 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:50 servername vmkernel: 0:12:06:30.448 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:50 servername vmkernel: 0:12:06:30.448 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:50 servername vmkernel: 0:12:06:30.448 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:50 servername vmkernel: 0:12:06:30.448 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:51 servername vmkernel: 0:12:06:30.648 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:51 servername vmkernel: 0:12:06:30.648 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:51 servername vmkernel: 0:12:06:30.648 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:51 servername vmkernel: 0:12:06:30.648 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:51 servername vmkernel: 0:12:06:30.848 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:51 servername vmkernel: 0:12:06:30.848 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:51 servername vmkernel: 0:12:06:30.848 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:51 servername vmkernel: 0:12:06:30.848 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:51 servername vmkernel: 0:12:06:31.048 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:51 servername vmkernel: 0:12:06:31.048 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:51 servername vmkernel: 0:12:06:31.048 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:51 servername vmkernel: 0:12:06:31.048 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:51 servername vmkernel: 0:12:06:31.248 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:51 servername vmkernel: 0:12:06:31.248 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:51 servername vmkernel: 0:12:06:31.248 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:51 servername vmkernel: 0:12:06:31.248 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:51 servername vmkernel: 0:12:06:31.448 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:51 servername vmkernel: 0:12:06:31.448 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:31.648 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:31.648 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:31.648 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:52 servername vmkernel: 0:12:06:31.648 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:52 servername vmkernel: 0:12:06:31.848 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:31.848 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:31.848 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:31.848 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:31.848 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:52 servername vmkernel: 0:12:06:31.848 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:52 servername vmkernel: 0:12:06:32.049 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:32.049 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:32.049 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:52 servername vmkernel: 0:12:06:32.049 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:52 servername vmkernel: 0:12:06:32.249 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:32.249 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:32.249 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:32.249 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:32.249 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:52 servername vmkernel: 0:12:06:32.249 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:52 servername vmkernel: 0:12:06:32.449 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:32.449 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:32.449 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:52 servername vmkernel: 0:12:06:32.449 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:52 servername vmkernel: 0:12:06:32.449 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:52 servername vmkernel: 0:12:06:32.449 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:53 servername vmkernel: 0:12:06:32.649 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:32.649 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:32.649 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:32.649 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:32.649 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:53 servername vmkernel: 0:12:06:32.649 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:53 servername vmkernel: 0:12:06:32.849 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:32.849 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:32.849 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:53 servername vmkernel: 0:12:06:32.849 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:53 servername vmkernel: 0:12:06:33.049 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:33.049 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:33.049 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:33.049 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:33.249 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:33.249 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:33.249 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:53 servername vmkernel: 0:12:06:33.249 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:53 servername vmkernel: 0:12:06:33.449 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:53 servername vmkernel: 0:12:06:33.449 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:53 servername vmkernel: 0:12:06:33.449 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:53 servername vmkernel: 0:12:06:33.449 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:54 servername vmkernel: 0:12:06:33.649 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:54 servername vmkernel: 0:12:06:33.649 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:54 servername vmkernel: 0:12:06:33.850 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:54 servername vmkernel: 0:12:06:33.850 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:54 servername vmkernel: 0:12:06:33.850 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:54 servername vmkernel: 0:12:06:33.850 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:54 servername vmkernel: 0:12:06:34.050 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:54 servername vmkernel: 0:12:06:34.050 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:54 servername vmkernel: 0:12:06:34.050 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:54 servername vmkernel: 0:12:06:34.050 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:54 servername vmkernel: 0:12:06:34.250 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:54 servername vmkernel: 0:12:06:34.250 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:54 servername vmkernel: 0:12:06:34.250 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:54 servername vmkernel: 0:12:06:34.250 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:54 servername vmkernel: 0:12:06:34.450 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:54 servername vmkernel: 0:12:06:34.450 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:55 servername vmkernel: 0:12:06:34.650 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:55 servername vmkernel: 0:12:06:34.650 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:55 servername vmkernel: 0:12:06:34.850 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:55 servername vmkernel: 0:12:06:34.850 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:55 servername vmkernel: 0:12:06:34.850 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:55 servername vmkernel: 0:12:06:34.850 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:55 servername vmkernel: 0:12:06:35.050 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:55 servername vmkernel: 0:12:06:35.050 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:55 servername vmkernel: 0:12:06:35.050 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:55 servername vmkernel: 0:12:06:35.050 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:55 servername vmkernel: 0:12:06:35.251 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:55 servername vmkernel: 0:12:06:35.251 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:55 servername vmkernel: 0:12:06:35.451 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:55 servername vmkernel: 0:12:06:35.451 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:56 servername vmkernel: 0:12:06:35.651 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:56 servername vmkernel: 0:12:06:35.651 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:56 servername vmkernel: 0:12:06:35.851 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:56 servername vmkernel: 0:12:06:35.851 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:56 servername vmkernel: 0:12:06:35.852 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:56 servername vmkernel: 0:12:06:35.852 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:56 servername vmkernel: 0:12:06:36.052 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:56 servername vmkernel: 0:12:06:36.052 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:56 servername vmkernel: 0:12:06:36.052 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:56 servername vmkernel: 0:12:06:36.052 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:56 servername vmkernel: 0:12:06:36.252 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:56 servername vmkernel: 0:12:06:36.252 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:56 servername vmkernel: 0:12:06:36.452 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:56 servername vmkernel: 0:12:06:36.452 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:57 servername vmkernel: 0:12:06:36.653 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:57 servername vmkernel: 0:12:06:36.653 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:57 servername vmkernel: 0:12:06:36.653 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:57 servername vmkernel: 0:12:06:36.653 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:57 servername vmkernel: 0:12:06:36.853 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:57 servername vmkernel: 0:12:06:36.853 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:57 servername vmkernel: 0:12:06:37.053 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:57 servername vmkernel: 0:12:06:37.053 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:57 servername vmkernel: 0:12:06:37.053 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:57 servername vmkernel: 0:12:06:37.053 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 01:44:57 servername vmkernel: 0:12:06:37.254 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:57 servername vmkernel: 0:12:06:37.254 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:57 servername vmkernel: 0:12:06:37.254 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:57 servername vmkernel: 0:12:06:37.254 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:57 servername vmkernel: 0:12:06:37.454 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:57 servername vmkernel: 0:12:06:37.454 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:57 servername vmkernel: 0:12:06:37.454 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:57 servername vmkernel: 0:12:06:37.454 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:58 servername vmkernel: 0:12:06:37.654 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:58 servername vmkernel: 0:12:06:37.654 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:58 servername vmkernel: 0:12:06:37.654 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:58 servername vmkernel: 0:12:06:37.654 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:58 servername vmkernel: 0:12:06:37.854 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:58 servername vmkernel: 0:12:06:37.854 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:58 servername vmkernel: 0:12:06:37.854 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:58 servername vmkernel: 0:12:06:37.854 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:58 servername vmkernel: 0:12:06:38.054 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:58 servername vmkernel: 0:12:06:38.054 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:58 servername vmkernel: 0:12:06:38.054 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:58 servername vmkernel: 0:12:06:38.054 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:58 servername vmkernel: 0:12:06:38.254 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:58 servername vmkernel: 0:12:06:38.254 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:58 servername vmkernel: 0:12:06:38.254 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:58 servername vmkernel: 0:12:06:38.254 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:58 servername vmkernel: 0:12:06:38.455 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:58 servername vmkernel: 0:12:06:38.455 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:58 servername vmkernel: 0:12:06:38.455 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:58 servername vmkernel: 0:12:06:38.455 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:59 servername vmkernel: 0:12:06:38.655 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:59 servername vmkernel: 0:12:06:38.655 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:59 servername vmkernel: 0:12:06:38.655 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:59 servername vmkernel: 0:12:06:38.655 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:59 servername vmkernel: 0:12:06:38.855 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:59 servername vmkernel: 0:12:06:38.855 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:59 servername vmkernel: 0:12:06:38.855 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:59 servername vmkernel: 0:12:06:38.855 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:59 servername vmkernel: 0:12:06:39.055 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:59 servername vmkernel: 0:12:06:39.055 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:59 servername vmkernel: 0:12:06:39.255 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:59 servername vmkernel: 0:12:06:39.255 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:59 servername vmkernel: 0:12:06:39.255 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:59 servername vmkernel: 0:12:06:39.255 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:44:59 servername vmkernel: 0:12:06:39.456 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:44:59 servername vmkernel: 0:12:06:39.456 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:44:59 servername vmkernel: 0:12:06:39.456 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:44:59 servername vmkernel: 0:12:06:39.456 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:45:00 servername vmkernel: 0:12:06:39.656 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:00 servername vmkernel: 0:12:06:39.656 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:45:00 servername vmkernel: 0:12:06:39.656 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:45:00 servername vmkernel: 0:12:06:39.656 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:45:00 servername vmkernel: 0:12:06:39.856 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:00 servername vmkernel: 0:12:06:39.856 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:45:00 servername vmkernel: 0:12:06:39.856 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:45:00 servername vmkernel: 0:12:06:39.856 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:45:00 servername vmkernel: 0:12:06:40.056 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:00 servername vmkernel: 0:12:06:40.056 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:45:00 servername vmkernel: 0:12:06:40.256 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:00 servername vmkernel: 0:12:06:40.256 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:45:00 servername vmkernel: 0:12:06:40.456 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:00 servername vmkernel: 0:12:06:40.456 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:45:00 servername vmkernel: 0:12:06:40.456 cpu2:1034)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 01:45:00 servername vmkernel: 0:12:06:40.456 cpu2:1034)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 01:45:01 servername vmkernel: 0:12:06:40.657 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:01 servername vmkernel: 0:12:06:40.657 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 01:45:01 servername vmkernel: 0:12:06:40.657 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 01:45:01 servername vmkernel: 0:12:06:40.657 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:18 servername vmkernel: 0:12:21:58.516 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:18 servername vmkernel: 0:12:21:58.516 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:18 servername vmkernel: 0:12:21:58.516 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:18 servername vmkernel: 0:12:21:58.516 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:19 servername vmkernel: 0:12:21:58.716 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:19 servername vmkernel: 0:12:21:58.716 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:19 servername vmkernel: 0:12:21:58.716 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:19 servername vmkernel: 0:12:21:58.716 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:19 servername vmkernel: 0:12:21:58.916 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:19 servername vmkernel: 0:12:21:58.916 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:19 servername vmkernel: 0:12:21:58.916 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:19 servername vmkernel: 0:12:21:58.916 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:19 servername vmkernel: 0:12:21:59.117 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:19 servername vmkernel: 0:12:21:59.117 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:19 servername vmkernel: 0:12:21:59.117 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:19 servername vmkernel: 0:12:21:59.117 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:19 servername vmkernel: 0:12:21:59.317 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:19 servername vmkernel: 0:12:21:59.317 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:19 servername vmkernel: 0:12:21:59.317 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:19 servername vmkernel: 0:12:21:59.317 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:19 servername vmkernel: 0:12:21:59.517 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:19 servername vmkernel: 0:12:21:59.517 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:19 servername vmkernel: 0:12:21:59.517 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:19 servername vmkernel: 0:12:21:59.517 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:20 servername vmkernel: 0:12:21:59.717 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:20 servername vmkernel: 0:12:21:59.717 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:20 servername vmkernel: 0:12:21:59.717 cpu1:1033)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:20 servername vmkernel: 0:12:21:59.717 cpu1:1033)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:20 servername vmkernel: 0:12:22:00.017 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:20 servername vmkernel: 0:12:22:00.017 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:20 servername vmkernel: 0:12:22:00.217 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:20 servername vmkernel: 0:12:22:00.217 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:20 servername vmkernel: 0:12:22:00.218 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:20 servername vmkernel: 0:12:22:00.218 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:20 servername vmkernel: 0:12:22:00.418 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:20 servername vmkernel: 0:12:22:00.418 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:20 servername vmkernel: 0:12:22:00.418 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:20 servername vmkernel: 0:12:22:00.418 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 02:00:21 servername vmkernel: 0:12:22:00.718 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:21 servername vmkernel: 0:12:22:00.718 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:21 servername vmkernel: 0:12:22:01.119 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:21 servername vmkernel: 0:12:22:01.119 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 02:00:21 servername vmkernel: 0:12:22:01.119 cpu1:1033)SCSI: 8043: vmhba0:0:2:1 status = 8/0 0x0 0x0 0x0
May 1 02:00:21 servername vmkernel: 0:12:22:01.119 cpu1:1033)SCSI: 8062: vmhba0:0:2:1 Retry (busy)
May 1 02:00:21 servername vmkernel: 0:12:22:01.420 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 02:00:21 servername vmkernel: 0:12:22:01.420 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like you have some serious SAN issues.
Starts with:
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.030 cpu1:1028)SCSI: 3753: AsyncIO timeout (5000); aborting cmd w/ sn 62, handle 1af2/0x6a01618.
At this point the LUNs are not responding and returning "status busy":
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.031 cpu1:1028)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
Then the SAN comes back momentarily, and ESX schedules a fsck (file system check) of the VMFS file systems.
Apr 30 21:56:49 servername vmkernel: 0:08:18:28.995 cpu2:1034)FS2: 1371: Scheduling maintenance on 41a27e6c-56bcce08-15f1-001185fed5a0. Last opener 0.0.0.0
Apr 30 21:56:49 servername vmkernel: 0:08:18:29.053 cpu2:1034)FS2: 8162: ** FS2Check summary **
Apr 30 21:56:49 servername vmkernel: 0:08:18:29.053 cpu2:1034)FS2: 8163: Return status: Success
15 Minutes later, you are back with the IO errors:
Apr 30 23:13:49 servername vmkernel: 0:09:35:29.476 cpu1:1028)SCSI: 3753: AsyncIO timeout (5000); aborting cmd w/ sn 74, handle 2001/0x6a015e8
Then LUN 0:0:1:1 goes busy and after a few seconds, the loop goes down.
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 00:46:00 servername vmkernel: 0:11:07:39.784 cpu2:1026)<6>scsi(0): LOOP DOWN detected.
May 1 00:46:11 servername vmkernel: 0:11:07:50.927 cpu2:1026)<6>scsi(0): LIP reset occurred.
Then it tries to change the active path:
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba0:1:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba0:2:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba0:3:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba1:0:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu2:1034)SCSI: 8043: vmhba1:0:1:1 status = 2/0 0x6 0x29 0x0
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu2:1034)SCSI: 8074: vmhba1:0:1:1 Retry (unit attn)
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:1:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:2:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:3:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba1:0:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:1:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:2:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:3:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba1:0:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba1:5:1 begins.
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)SCSI: 1789: Changing active path to vmhba1:5:1
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)WARNING: SCSI: 1110: Did not switchover to vmhba1:5:1. Check Unit Ready Command returned READY instead of NOT READY for standby controller .
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)WARNING: SCSI: 1820: Manual switchover to vmhba1:5:1 completed successfully.
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba1:5:2 begins.
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)SCSI: 1789: Changing active path to vmhba1:5:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)WARNING: SCSI: 1110: Did not switchover to vmhba1:5:2. Check Unit Ready Command returned READY instead of NOT READY for standby controller .
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)WARNING: SCSI: 1820: Manual switchover to vmhba1:5:2 completed successfully.
May 1 00:46:30 servername vmkernel: 0:11:08:09.794 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic0 cmd=0x8946 ifr=ce79deb4 status=0x2bacffa1
May 1 00:46:30 servername vmkernel: 0:11:08:09.904 cpu1:1025)<6>scsi(0): LOOP DEAD detected.
May 1 00:46:30 servername vmkernel: 0:11:08:09.967 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic2 cmd=0x8946 ifr=ce79deb4 status=0x2bacffa1
May 1 00:46:33 servername vmkernel: 0:11:08:12.904 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:46:33 servername vmkernel: 0:11:08:12.904 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:46:33 servername vmkernel: 0:11:08:12.905 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
Then the active path seems to come back to life:
May 1 00:47:11 servername vmkernel: 0:11:08:51.149 cpu2:1026)<6>scsi(0): LOOP UP detected.
Then it goes back down, then back up:
May 1 00:48:32 servername vmkernel: 0:11:10:12.258 cpu2:1026)<6>scsi(0): LOOP DOWN detected.
May 1 00:48:50 servername vmkernel: 0:11:10:30.142 cpu2:1026)<6>scsi(0): LIP reset occurred.
May 1 00:48:53 servername vmkernel: 0:11:10:33.279 cpu2:1026)<6>scsi(0): LOOP UP detected.
Then its back down again:
May 1 00:49:22 servername vmkernel: 0:11:11:01.629 cpu2:1026)<6>scsi(0): LOOP DOWN detected.
Then its back up:
May 1 00:49:49 servername vmkernel: 0:11:11:28.878 cpu2:1026)<6>scsi(0): LOOP UP detected.
May 1 00:49:49 servername vmkernel: 0:11:11:28.878 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:49 servername vmkernel: 0:11:11:28.878 cpu0:1050)scsi(0): Waiting for LIP to complete...
May 1 00:49:49 servername vmkernel: 0:11:11:29.128 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:49 servername vmkernel: 0:11:11:29.130 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:49 servername vmkernel: 0:11:11:29.132 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:53 servername vmkernel: 0:11:11:32.940 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.940 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.941 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.941 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.941 cpu1:1040)SCSI: 8074: vmhba1:0:2:0 Retry (unit attn)
But still in a busy state.
And the process repeats itself......
Yes, serious SAN issues. Make sure to check the logs in the SAN swithces, many times people overlook this log file but its often the most informative.
Does not look like ESX is the root cause of the problem. If the SAN was the cause you should have had an alarm generated there and been alerted.
Since the switches sit in between the SAN and ESX, I would see what their logs have to say about this. But something is interrupting communication back to the SAN.
my 2 cents
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please give a little more details:
\- multipathin (yes/no), which policy (Fixed, MRU)
\- which storage/hba/fc switch; zoning yes/no
\- have you checked your hba's bios (configured with "Point to Point" or "FC_AL")
maybe paste following:
"esxcfg-mpath -l"
"vdf"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Multipath - yes
Policy - Fixed on EVA 8000 Active/Active - MRU on EVA 5000 Active/Passive
Storage - EVA 8000 and EVA 5000
HBA - Qlogic 2312 with firmware 1.85
FC Switch - Brocade 232 432 isl link between 2 master swtiches and secondary switches.
HBA Bios - was set to disabled I have now enabled it but can not see where to check the setting you mentioned.
RAID Controller (SCSI-3) vmhba0:0:0 (0MB) has 8 paths and policy of Fixed
FC 6:3.0 500508b200bc3fb2<->50001fe150091359 vmhba0:0:0 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe15009135d vmhba0:1:0 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135b vmhba0:2:0 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135f vmhba0:3:0 On
FC 6:3.1 500508b200bc3fb3<->50001fe150091358 vmhba1:0:0 On
FC 6:3.1 500508b200bc3fb3<->50001fe15009135a vmhba1:1:0 On
FC 6:3.1 500508b200bc3fb3<->50001fe15009135c vmhba1:2:0 On
FC 6:3.1 500508b200bc3fb3<->50001fe15009135e vmhba1:3:0 On
RAID Controller (SCSI-3) vmhba0:4:0 (0MB) has 4 paths and policy of Most Recent
ly Used
FC 6:3.0 500508b200bc3fb2<->50001fe1500406bd vmhba0:4:0 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe1500406b8 vmhba0:5:0 Standby
FC 6:3.1 500508b200bc3fb3<->50001fe1500406b9 vmhba1:4:0 Standby
FC 6:3.1 500508b200bc3fb3<->50001fe1500406bc vmhba1:5:0 Standby
Disk vmhba0:4:1 /dev/sdd (204800MB) has 4 paths and policy of Most Recently Used
FC 6:3.0 500508b200bc3fb2<->50001fe1500406bd vmhba0:4:1 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe1500406b8 vmhba0:5:1 Standby
FC 6:3.1 500508b200bc3fb3<->50001fe1500406b9 vmhba1:4:1 Standby
FC 6:3.1 500508b200bc3fb3<->50001fe1500406bc vmhba1:5:1 On
Disk vmhba0:4:2 /dev/sde (768000MB) has 4 paths and policy of Most Recently Used
FC 6:3.0 500508b200bc3fb2<->50001fe1500406bd vmhba0:4:2 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe1500406b8 vmhba0:5:2 Standby
FC 6:3.1 500508b200bc3fb3<->50001fe1500406b9 vmhba1:4:2 Standby
FC 6:3.1 500508b200bc3fb3<->50001fe1500406bc vmhba1:5:2 On
Disk vmhba0:0:1 /dev/sda (2096128MB) has 4 paths and policy of Fixed
FC 6:3.0 500508b200bc3fb2<->50001fe150091359 vmhba0:0:1 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe15009135d vmhba0:1:1 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135b vmhba0:2:1 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135f vmhba0:3:1 On
Disk vmhba0:0:2 /dev/sdb (2096128MB) has 4 paths and policy of Fixed
FC 6:3.0 500508b200bc3fb2<->50001fe150091359 vmhba0:0:2 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe15009135d vmhba0:1:2 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135b vmhba0:2:2 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135f vmhba0:3:2 On
Disk vmhba0:0:3 /dev/sdc (102400MB) has 4 paths and policy of Fixed
FC 6:3.0 500508b200bc3fb2<->50001fe150091359 vmhba0:0:3 On active preferred
FC 6:3.0 500508b200bc3fb2<->50001fe15009135d vmhba0:1:3 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135b vmhba0:2:3 On
FC 6:3.0 500508b200bc3fb2<->50001fe15009135f vmhba0:3:3 On
Disk vmhba2:0:0 /dev/cciss/c0d0 (139979MB) has 1 paths and policy of Fixed
Local 8:8.0 vmhba2:0:0 On active preferred
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/cciss/c0d0p2 5036316 2007984 2772500 43% /
/dev/cciss/c0d0p1 101089 31854 64016 34% /boot
/dev/cciss/c0d0p7 505605 8244 471257 2% /home
none 134124 0 134124 0% /dev/shm
/dev/cciss/c0d0p5 8064272 34728 7619892 1% /tmp
/dev/cciss/c0d0p6 2529920 52392 2349012 3% /var/log
/vmfs/devices 10060246082 010060246082 0% /vmfs/devices
/vmfs/volumes/415652ce-561c3020-49b6-0012793be16c
786414592 744488960 41925632 94% /vmfs/volumes/SANEVADATA
D2
/vmfs/volumes/41a27e6c-56bcce08-15f1-001185fed5a0
104848384 43157504 61690880 41% /vmfs/volumes/41a27e6c-5
6bcce08-15f1-001185fed5a0
/vmfs/volumes/45622180-e431f556-86d5-001a4bd15486
104595456 32105472 72489984 30% /vmfs/volumes/SANEVA02_V
MFS3_Server_Templates
/vmfs/volumes/4564b53e-2bbe1a35-8b8b-001a4bd15486
126091264 642048 125449216 0% /vmfs/volumes/storage1
/vmfs/volumes/456f5f7b-7360b47e-b0a4-001a4bd15486
214617292811146567681031516160 51% /vmfs/volumes/SANEVA02_V
MFS3_D1
/vmfs/volumes/456f7b30-b89d7399-e2a9-001a4bd15486
21461729281376260096 769912832 64% /vmfs/volumes/SANEVA02_V
MFS3_D2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like you have some serious SAN issues.
Starts with:
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.030 cpu1:1028)SCSI: 3753: AsyncIO timeout (5000); aborting cmd w/ sn 62, handle 1af2/0x6a01618.
At this point the LUNs are not responding and returning "status busy":
Apr 30 21:05:36 servername vmkernel: 0:07:27:16.031 cpu1:1028)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
Then the SAN comes back momentarily, and ESX schedules a fsck (file system check) of the VMFS file systems.
Apr 30 21:56:49 servername vmkernel: 0:08:18:28.995 cpu2:1034)FS2: 1371: Scheduling maintenance on 41a27e6c-56bcce08-15f1-001185fed5a0. Last opener 0.0.0.0
Apr 30 21:56:49 servername vmkernel: 0:08:18:29.053 cpu2:1034)FS2: 8162: ** FS2Check summary **
Apr 30 21:56:49 servername vmkernel: 0:08:18:29.053 cpu2:1034)FS2: 8163: Return status: Success
15 Minutes later, you are back with the IO errors:
Apr 30 23:13:49 servername vmkernel: 0:09:35:29.476 cpu1:1028)SCSI: 3753: AsyncIO timeout (5000); aborting cmd w/ sn 74, handle 2001/0x6a015e8
Then LUN 0:0:1:1 goes busy and after a few seconds, the loop goes down.
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1026)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1026)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1034)SCSI: 8043: vmhba0:0:1:1 status = 8/0 0x0 0x0 0x0
May 1 00:45:57 servername vmkernel: 0:11:07:37.612 cpu2:1034)SCSI: 8062: vmhba0:0:1:1 Retry (busy)
May 1 00:46:00 servername vmkernel: 0:11:07:39.784 cpu2:1026)<6>scsi(0): LOOP DOWN detected.
May 1 00:46:11 servername vmkernel: 0:11:07:50.927 cpu2:1026)<6>scsi(0): LIP reset occurred.
Then it tries to change the active path:
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba0:1:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba0:2:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba0:3:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu0:1029)SCSI: 1789: Changing active path to vmhba1:0:1
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu2:1034)SCSI: 8043: vmhba1:0:1:1 status = 2/0 0x6 0x29 0x0
May 1 00:46:29 servername vmkernel: 0:11:08:08.904 cpu2:1034)SCSI: 8074: vmhba1:0:1:1 Retry (unit attn)
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:1:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:2:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:3:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.134 cpu2:1026)SCSI: 1789: Changing active path to vmhba1:0:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:1:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:2:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba0:3:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.355 cpu2:1026)SCSI: 1789: Changing active path to vmhba1:0:3
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba1:5:1 begins.
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)SCSI: 1789: Changing active path to vmhba1:5:1
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)WARNING: SCSI: 1110: Did not switchover to vmhba1:5:1. Check Unit Ready Command returned READY instead of NOT READY for standby controller .
May 1 00:46:29 servername vmkernel: 0:11:08:09.522 cpu1:1038)WARNING: SCSI: 1820: Manual switchover to vmhba1:5:1 completed successfully.
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba1:5:2 begins.
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)SCSI: 1789: Changing active path to vmhba1:5:2
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)WARNING: SCSI: 1110: Did not switchover to vmhba1:5:2. Check Unit Ready Command returned READY instead of NOT READY for standby controller .
May 1 00:46:29 servername vmkernel: 0:11:08:09.558 cpu1:1038)WARNING: SCSI: 1820: Manual switchover to vmhba1:5:2 completed successfully.
May 1 00:46:30 servername vmkernel: 0:11:08:09.794 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic0 cmd=0x8946 ifr=ce79deb4 status=0x2bacffa1
May 1 00:46:30 servername vmkernel: 0:11:08:09.904 cpu1:1025)<6>scsi(0): LOOP DEAD detected.
May 1 00:46:30 servername vmkernel: 0:11:08:09.967 cpu0:1024)VMNIX: VmkDev: 3293: dev=vmnic2 cmd=0x8946 ifr=ce79deb4 status=0x2bacffa1
May 1 00:46:33 servername vmkernel: 0:11:08:12.904 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:46:33 servername vmkernel: 0:11:08:12.904 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:46:33 servername vmkernel: 0:11:08:12.905 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
Then the active path seems to come back to life:
May 1 00:47:11 servername vmkernel: 0:11:08:51.149 cpu2:1026)<6>scsi(0): LOOP UP detected.
Then it goes back down, then back up:
May 1 00:48:32 servername vmkernel: 0:11:10:12.258 cpu2:1026)<6>scsi(0): LOOP DOWN detected.
May 1 00:48:50 servername vmkernel: 0:11:10:30.142 cpu2:1026)<6>scsi(0): LIP reset occurred.
May 1 00:48:53 servername vmkernel: 0:11:10:33.279 cpu2:1026)<6>scsi(0): LOOP UP detected.
Then its back down again:
May 1 00:49:22 servername vmkernel: 0:11:11:01.629 cpu2:1026)<6>scsi(0): LOOP DOWN detected.
Then its back up:
May 1 00:49:49 servername vmkernel: 0:11:11:28.878 cpu2:1026)<6>scsi(0): LOOP UP detected.
May 1 00:49:49 servername vmkernel: 0:11:11:28.878 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:49 servername vmkernel: 0:11:11:28.878 cpu0:1050)scsi(0): Waiting for LIP to complete...
May 1 00:49:49 servername vmkernel: 0:11:11:29.128 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:49 servername vmkernel: 0:11:11:29.130 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:49 servername vmkernel: 0:11:11:29.132 cpu2:1026)<6>scsi(0): Port database changed.
May 1 00:49:53 servername vmkernel: 0:11:11:32.940 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.940 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.941 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.941 cpu1:1040)SCSI: 8074: vmhba1:0:1:0 Retry (unit attn)
May 1 00:49:53 servername vmkernel: 0:11:11:32.941 cpu1:1040)SCSI: 8074: vmhba1:0:2:0 Retry (unit attn)
But still in a busy state.
And the process repeats itself......
Yes, serious SAN issues. Make sure to check the logs in the SAN swithces, many times people overlook this log file but its often the most informative.
Does not look like ESX is the root cause of the problem. If the SAN was the cause you should have had an alarm generated there and been alerted.
Since the switches sit in between the SAN and ESX, I would see what their logs have to say about this. But something is interrupting communication back to the SAN.
my 2 cents
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi thanks for your reply it has been very helpful,
one of our primary switches has a number of ports going from healthy to marginal constantly would this cause errors or just slow down performance?
regards,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just found marginal to down errors so looks like you have pointed out the issue I will get back to you.
thank you,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thanks for you great breakdown of what is happening here. I had a “non disruptive” FLARE code upgrade to a Clariion CX3-20 produce similar logs and knock Linux VM’s into read only root disks. The upgrade procedure took one service processor offline, which should have caused a path failure in VMware, thus switching over to an alternate path. But it seems the failover took considerable time, as indicated by my logs below.
System setup:
5 Dell PowerEdge 2950’s running ESX 3.0.1 with no patches. 2 QLA2432 (that’s what VMware ID’s them as anyway) going to 2 Qlogic SANBOX 5202 switches, which in turn each have 2 connections to the Clariion.
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.965 cpu0:1028)SCSI: 3731: AsyncIO timeout (5000); aborting cmd w/ sn 3326855, handle 2169/0x7201410
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.965 cpu0:1028)LinSCSI: 3596: Aborting cmds with world 1024, originHandle 0x7201410, originSN 3326855 from vmhba2:0:0
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.965 cpu0:1028)<6>qla24xx_abort_command(1): handle to abort=1953
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)SCSI: 3731: AsyncIO timeout (5000); aborting cmd w/ sn 3539356, handle 216f/0x7201278
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)LinSCSI: 3596: Aborting cmds with world 1024, originHandle 0x7201278, originSN 3539356 from vmhba2:0:2
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)<6>qla24xx_abort_command(1): handle to abort=1952
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)LinSCSI: 2604: Forcing host status from 2 to SCSI_HOST_OK
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.966 cpu3:1028)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.866 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba2:2:0 begins.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.866 cpu1:1038)SCSI: 1789: Changing active path to vmhba2:2:0
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.866 cpu3:1038)SCSI: 1072: Could not switchover to vmhba2:2:0. Check Unit Ready Command failed AFTER Start Unit: Not ready
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.866 cpu3:1038)WARNING: SCSI: 1828: Manual switchover to vmhba2:2:0 completed unsuccessfully.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.867 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba3:0:0 begins.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.867 cpu1:1038)SCSI: 1789: Changing active path to vmhba3:0:0
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.868 cpu1:1038)SCSI: 1072: Could not switchover to vmhba3:0:0. Check Unit Ready Command failed AFTER Start Unit: Not ready
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.868 cpu1:1038)WARNING: SCSI: 1828: Manual switchover to vmhba3:0:0 completed unsuccessfully.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.869 cpu2:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba3:2:0 begins.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.869 cpu2:1038)SCSI: 1789: Changing active path to vmhba3:2:0
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.869 cpu2:1038)SCSI: 1072: Could not switchover to vmhba3:2:0. Check Unit Ready Command failed AFTER Start Unit: Not ready
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.869 cpu2:1038)WARNING: SCSI: 1828: Manual switchover to vmhba3:2:0 completed unsuccessfully.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.870 cpu0:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba3:3:0 begins.
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.870 cpu0:1038)SCSI: 1789: Changing active path to vmhba3:3:0
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.926 cpu3:1038)SCSI: 8052: vmhba3:3:0:1 Retry (unit attn)
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.926 cpu3:1038)WARNING: SCSI: 1820: Manual switchover to vmhba3:3:0 completed successfully.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.720 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba2:2:1 begins.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.720 cpu1:1038)SCSI: 1789: Changing active path to vmhba2:2:1
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.720 cpu1:1038)SCSI: 1072: Could not switchover to vmhba2:2:1. Check Unit Ready Command failed AFTER Start Unit: Not ready
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.720 cpu1:1038)WARNING: SCSI: 1828: Manual switchover to vmhba2:2:1 completed unsuccessfully.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.721 cpu2:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba3:0:1 begins.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.721 cpu2:1038)SCSI: 1789: Changing active path to vmhba3:0:1
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.722 cpu1:1038)SCSI: 1072: Could not switchover to vmhba3:0:1. Check Unit Ready Command failed AFTER Start Unit: Not ready
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.722 cpu1:1038)WARNING: SCSI: 1828: Manual switchover to vmhba3:0:1 completed unsuccessfully.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.723 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba3:2:1 begins.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.723 cpu1:1038)SCSI: 1789: Changing active path to vmhba3:2:1
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.723 cpu3:1038)SCSI: 1072: Could not switchover to vmhba3:2:1. Check Unit Ready Command failed AFTER Start Unit: Not ready
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.723 cpu3:1038)WARNING: SCSI: 1828: Manual switchover to vmhba3:2:1 completed unsuccessfully.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.724 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba3:3:1 begins.
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.724 cpu1:1038)SCSI: 1789: Changing active path to vmhba3:3:1
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.765 cpu2:1038)SCSI: 8052: vmhba3:3:1:1 Retry (unit attn)
May 17 11:37:22 bazooka vmkernel: 113:18:42:51.765 cpu2:1038)WARNING: SCSI: 1820: Manual switchover to vmhba3:3:1 completed successfully.
May 17 11:39:54 bazooka vmkernel: 113:18:45:24.178 cpu2:1040)SCSI: 8052: vmhba3:3:0:0 Retry (unit attn)
May 17 11:39:54 bazooka vmkernel: 113:18:45:24.179 cpu1:1040)SCSI: 8052: vmhba3:3:0:0 Retry (unit attn)
May 17 11:39:54 bazooka vmkernel: 113:18:45:24.179 cpu1:1040)SCSI: 8052: vmhba3:3:0:0 Retry (unit attn)
May 17 11:39:54 bazooka vmkernel: 113:18:45:24.179 cpu2:1040)SCSI: 8052: vmhba3:3:1:0 Retry (unit attn)
May 17 11:39:54 bazooka vmkernel: 113:18:45:24.180 cpu0:1040)SCSI: 8052: vmhba3:3:1:0 Retry (unit attn)
May 17 11:39:54 bazooka vmkernel: 113:18:45:24.180 cpu3:1040)SCSI: 8052: vmhba3:3:1:0 Retry (unit attn)
The way that I interpret these logs, the first sign of trouble appears at:
May 17 11:11:03 bazooka vmkernel: 113:18:16:32.965 cpu0:1028)SCSI: 3731: AsyncIO timeout (5000); aborting cmd w/ sn 3326855, handle 2169/0x7201410
However, failover doesn’t begin until:
May 17 11:37:21 bazooka vmkernel: 113:18:42:50.866 cpu1:1038)WARNING: SCSI: 1785: Manual switchover to path vmhba2:2:0 begins.
This is 26 minutes after the first sign of a problem. Am I interrupting the logs wrong? Is AsyncIO timeout not a big deal (it sure seems like it to me)? What exactly does that mean? Does it mean that the IO (presumably from the guest OS) is simply queued? Is the guest told that the IO completed? Is it told to retry?
In the SAN System Design and Deployment Guide (March 2007), it says “Thus, it is recommended that you set the virtual machine Disk TimeOutValue setting to at least 60 seconds to allow SCSI devices and path selection time to stabilize during a physical path disruption.”
What about for Linux? Can I change these settings so that they equate to 60 seconds?:
From scsi.h,
#define FORMAT_UNIT_TIMEOUT (2 * 60 * 60 * HZ)
#define START_STOP_TIMEOUT (60 * HZ)
#define MOVE_MEDIUM_TIMEOUT (5 * 60 * HZ)
#define READ_ELEMENT_STATUS_TIMEOUT (5 * 60 * HZ)
#define READ_DEFECT_DATA_TIMEOUT (60 * HZ)
TIA
Brad