Veritas-bu

Re: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) timeout question

2012-04-16 08:09:28
Subject: Re: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) timeout question
From: nbuser <nbuser AT live DOT com>
To: Justin Piszcz <jpiszcz AT lucidpixels DOT com>
Date: Mon, 16 Apr 2012 05:07:57 -0700
We use QLogic and we seem to have found workaround.

Whenever drives go down we reset the down drive ports from the switch side and then drives come up. Now we don't need to reset the drives physically.

On Mon, Apr 16, 2012 at 4:01 AM, Justin Piszcz <jpiszcz AT lucidpixels DOT com> wrote:
Hi,

Could you please elaborate on this?

Additionally, what are you (and others) using when it comes to the
fiber side on the media server? QLogic? Emulex?

Have you found any workarounds?

Justin.

On Tue, Apr 10, 2012 at 11:42 AM, nbuser <nbuser AT live DOT com> wrote:
> We also face this issue where we have to reseat the drive's fibre cable and
> power recycle the drive. In our environment we have HP LTO-5  in Quantum
> i6000 series tape library. Problem is sometimes drives go down and we have
> to do the above mentioned steps to bring them UP. We also have encryption
> enabled on them.
>
> On Tue, Apr 10, 2012 at 5:16 AM, Justin Piszcz <jpiszcz AT lucidpixels DOT com>
> wrote:
>>
>> Hi,
>>
>>
>>
>> Was curious if anyone had been running into timeouts with IBM LTO-5 drives
>> in heavily utilized environments with QLOGIC 2562-CK (8GBPS) HBAs?
>>
>> Never saw this in smaller environments with MPX <= 3 but now with MPX >= 6
>> some drives seem to be timing out and going into a “hung” state.
>>
>> Was curious if anyone ever ran into this issue before?
>>
>> Power cycling the drive (reseating it) fixes it and then it’s fine again
>> as a workaround but not a fix, thoughts?
>>
>> F/W on the IBM LTO-5 drives is BBN2 (latest from Oracle)
>>
>> F/W on the HBA’s is 3.00 (latest from QLogic)
>>
>>
>>
>> When the problem occurs (these errors spew continuously) until the drive
>> is reseated (rebooting the robot does not clear out the errors)
>>
>> st 3:0:0:0: timing out command, waited 7s
>>
>> qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e08 2002.
>>
>> st 3:0:0:0: timing out command, waited 7s
>>
>> qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e0a 2002.
>>
>> st 3:0:0:0: timing out command, waited 7s
>>
>> qla2xxx 0000:0d:00.0: scsi(0:0:0): Abort command issued -- 1 1820 2002.
>>
>> qla2xxx 0000:0d:00.0: scsi(0:0:0): Abort command issued -- 1 1821 2002.
>>
>> st 0:0:0:0: timing out command, waited 900s
>>
>> st0: Error 6080000 (sugg. bt 0x0, driver bt 0x6, host bt 0x8).
>>
>> st 0:0:0:0: timing out command, waited 180s
>>
>> qla2xxx 0000:0d:00.0: scsi(0:0:0): Abort command issued -- 1 1823 2002.
>>
>> st 0:0:0:0: timing out command, waited 60s
>>
>> qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e18 2002.
>>
>> st 3:0:0:0: timing out command, waited 7s
>>
>> qla2xxx 0000:0a:00.1: scsi(3:0:0): Abort command issued -- 1 e1a 2002.
>>
>> st 3:0:0:0: timing out command, waited 7s
>>
>>
>>
>> Justin.
>>
>>
>> _______________________________________________
>> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu