X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8BACF.A1D75B5F@onstor-exch02.onstor.net>; Tue, 20 May 2008 16:17:11 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8BACF.A1D75B5F"
Content-class: urn:content-classes:message
Subject: RE: scsi: ispfc  "should never happen unless link is up"
Date: Tue, 20 May 2008 16:17:11 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08FC5AA1@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0A0F89A0@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: scsi: ispfc  "should never happen unless link is up"
Thread-Index: Aci6uYX8ovwdfFyDTNuaLumS9+0NxQAFgOHg
From: "Bill Nadzam" <bill.nadzam@onstor.com>
To: "Rich LaReau" <rich.lareau@onstor.com>,
	"dl-cstech" <dl-cstech@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8BACF.A1D75B5F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There isn't much more to say except the port times out.
Looks like the device is not responding.

> _____________________________________________=20
> From: 	Rich LaReau =20
> Sent:	Tuesday, May 20, 2008 1:39 PM
> To:	dl-cstech
> Subject:	scsi: ispfc  "should never happen unless link is up"
>=20
>=20
> In the midst of lots of I/O retries, we see these sets of logs.  I'm
> curious if they indicate anything other than a bad drive failing on
> the storage array, or some problem with the SAN in general.  In
> particular, what's the meaning of the red error?
>=20
>=20
> May 20 11:13:02 fss-pnasgw1 : 1:2:evm:WARNING: 1229: [][]: 5 I/O
> retries for volume[IDR-FC].
> May 20 11:13:04 fss-pnasgw1 : 1:2:evm:WARNING: 1230: [][]: 28 I/O
> retries for volume[IDR-FC].
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1869: ispfc:sp2.0:
> ispfc_dev_abort_taskset: phys_dev_id 0x11b00, handle 0=20
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1870: ispfc:sp2.0:
> WWN:200300a0b80f6b20:0, cdb 0x2a:0a7dd100:0010, cs[0005] ss[0000]
> fcp[N/A] retryCnt 3=20
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1871: ispfc:sp2.0:
> ISPFC_CS_RESET_OCCURRED: Pause device [0x11b00], command count [2]
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1872: ispfc:sp2.0:
> ispfc_dev_tmo_common_callback_0: phys_dev_id 0x11b00, handle 0=20
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1873: ispfc:sp2.0:
> ispfc_dev_tmo_common_callback_0: Starting queue flush timer,
> phys_dev_id 0x11b00, handle 0=20
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1874: ispfc:sp2.0:
> WWN:200300a0b80f6b20:0, cdb 0x2a:00058590:0010, cs[0005] ss[0000]
> fcp[N/A] retryCnt 3=20
> May 20 11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1875: ispfc:sp2.0:
> ISPFC_CS_RESET_OCCURRED: Pause device [0x11b00], command count [1]
> May 20 11:13:08 fss-pnasgw1 : 2:0:scsi:NOTICE: 1876: ispfc:sp2.0:
> ispfc_dev_tmo_common_callback_1: phys_dev_id 0x11b00, handle 0=20
> May 20 11:13:08 fss-pnasgw1 : 2:0:scsi:NOTICE: 1877: ispfc:sp2.0:
> WWN:200300a0b80f6b20:0, cdb 0x2a:1de8f570:0050, cs[0006] ss[0000]
> fcp[N/A] retryCnt 3=20
> May 20 11:13:08 fss-pnasgw1 : 2:0:scsi:NOTICE: 1878: ispfc:sp2.0:
> ISPFC_CS_TIMEOUT: device [0x11b00], should never happen unless link is
> up.
> May 20 11:13:08 fss-pnasgw1 : 2:0:scsi:ERROR: 1879: scsi: eCode(10)
> caused by bad drv_status [0x09]  dev_status[0x00]=20

------_=_NextPart_001_01C8BACF.A1D75B5F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: scsi: ispfc  &quot;should never happen unless link is =
up&quot;</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">There isn't much more to say except the port times =
out.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Looks like the device is not responding.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: =
&nbsp;</FONT></B> <FONT SIZE=3D1 FACE=3D"Tahoma">Rich LaReau&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Tuesday, May 20, 2008 1:39 PM</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">dl-cstech</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">scsi: ispfc&nbsp; &quot;should never =
happen unless link is up&quot;</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">In the midst of =
lots of I/O retries, we see these sets of logs.&nbsp; I'm curious if =
they indicate anything other than a bad drive failing on the storage =
array, or some problem with the SAN in general.&nbsp; In particular, =
what's the meaning of </FONT><FONT COLOR=3D"#FF0000" SIZE=3D2 =
FACE=3D"Arial">the red error?</FONT></SPAN></P>
<BR>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:02 fss-pnasgw1 : 1:2:evm:WARNING: 1229: [][]: 5 I/O retries for =
volume[IDR-FC].</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:04 fss-pnasgw1 : 1:2:evm:WARNING: 1230: [][]: 28 I/O retries for =
volume[IDR-FC].</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1869: ispfc:sp2.0: =
ispfc_dev_abort_taskset: phys_dev_id 0x11b00, handle 0 =
</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1870: ispfc:sp2.0: =
WWN:200300a0b80f6b20:0, cdb 0x2a:0a7dd100:0010, cs[0005] ss[0000] =
fcp[N/A] retryCnt 3 </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1871: ispfc:sp2.0: =
ISPFC_CS_RESET_OCCURRED: Pause device [0x11b00], command count =
[2]</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1872: ispfc:sp2.0: =
ispfc_dev_tmo_common_callback_0: phys_dev_id 0x11b00, handle 0 =
</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1873: ispfc:sp2.0: =
ispfc_dev_tmo_common_callback_0: Starting queue flush timer, phys_dev_id =
0x11b00, handle 0 </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1874: ispfc:sp2.0: =
WWN:200300a0b80f6b20:0, cdb 0x2a:00058590:0010, cs[0005] ss[0000] =
fcp[N/A] retryCnt 3 </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:06 fss-pnasgw1 : 2:0:scsi:NOTICE: 1875: ispfc:sp2.0: =
ISPFC_CS_RESET_OCCURRED: Pause device [0x11b00], command count =
[1]</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:08 fss-pnasgw1 : 2:0:scsi:NOTICE: 1876: ispfc:sp2.0: =
ispfc_dev_tmo_common_callback_1: phys_dev_id 0x11b00, handle 0 =
</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:08 fss-pnasgw1 : 2:0:scsi:NOTICE: 1877: ispfc:sp2.0: =
WWN:200300a0b80f6b20:0, cdb 0x2a:1de8f570:0050, cs[0006] ss[0000] =
fcp[N/A] retryCnt 3 </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Courier =
New">May 20 11:13:08 fss-pnasgw1 : 2:0:scsi:NOTICE: 1878: ispfc:sp2.0: =
ISPFC_CS_TIMEOUT: device [0x11b00], should never happen unless link is =
up.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">May 20 =
11:13:08 fss-pnasgw1 : 2:0:scsi:ERROR: 1879: scsi: eCode(10) caused by =
bad drv_status [0x09]&nbsp; dev_status[0x00]</FONT> </SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8BACF.A1D75B5F--
