vmhba1:0:6:0 Retry (unit attn)

[rminick]

Can anyone give any input on what could be causing these errors? I'm see similar vmkernel errors on all 4 nodes in a cluster attched to our EVA8000. I'm not seeing any issues with any of the guests. I don't see anything of value in our Brocade switch logs or Commandview. Could it be a path going up & down? I would think I'd see something in the logs for the SAN devices.

Aug 24 02:03:52 ESXHost vmkernel: 7:17:16:04.071 cpu1:1136)LinSCSI: 2604: Forcing host status from 7 to SCSI_HOST_OK

Aug 24 06:13:23 ESXHost vmkernel: 7:21:25:35.617 cpu5:1044)SCSI: 8053: vmhba1:0:6:0 Retry (unit attn)

Aug 24 11:13:44 ESXHost vmkernel: 8:02:25:56.432 cpu7:1340)LinSCSI: 2606: Forcing device status from SDSTAT_GOOD to SDSTAT_BUSY

Aug 24 11:13:44 ESXHost vmkernel: 8:02:25:56.432 cpu0:1044)SCSI: 8041: vmhba1:0:1:0 Retry (busy)

[MattG]

They just look like normal status messages from the SAN. Though Retry Busy doesn't sound good?

We had a bunch of SCSI warnings in the VM Log files that we ended up suppressing on the Hitachi SAN side because they were not really warnings.

-MattG