Hi, Issue found for this one, F/W needs to be 1432 and not 1395 (current) for LTO-5 (I knew this but did not do this upgrade). Getting this fixed, then need to figure out the encryption issue.
Justin. On Tue, Apr 10, 2012 at 10:48 PM, Steve Quan <sk...@hotmail.com> wrote: > Any indications from the lights on the tapedrive before it's reseated ? Can > you get logs from the library ? > > /Steve > >> From: veritas-bu-requ...@mailman.eng.auburn.edu >> Subject: Veritas-bu Digest, Vol 72, Issue 7 >> To: veritas-bu@mailman.eng.auburn.edu >> Date: Tue, 10 Apr 2012 12:00:02 -0500 >> >> Send Veritas-bu mailing list submissions to >> veritas-bu@mailman.eng.auburn.edu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> or, via email, send a message with subject or body 'help' to >> veritas-bu-requ...@mailman.eng.auburn.edu >> >> You can reach the person managing the list at >> veritas-bu-ow...@mailman.eng.auburn.edu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Veritas-bu digest..." >> >> >> Today's Topics: >> >> 1. IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) timeout >> question (Justin Piszcz) >> 2. Re: IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) >> timeout question (Len Boyle) >> 3. Re: IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) >> timeout question (Justin Piszcz) >> 4. Re: IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) >> timeout question (nbuser) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 10 Apr 2012 08:16:00 -0400 >> From: "Justin Piszcz" <jpis...@lucidpixels.com> >> Subject: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps >> HBA) timeout question >> To: <veritas-bu@mailman.eng.auburn.edu> >> Message-ID: <001b01cd1713$b15704e0$14050ea0$@lucidpixels.com> >> Content-Type: text/plain; charset="us-ascii" >> >> 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. >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20120410/f51ded44/attachment-0001.htm >> >> ------------------------------ >> >> Message: 2 >> Date: Tue, 10 Apr 2012 12:19:21 +0000 >> From: Len Boyle <len.bo...@sas.com> >> Subject: Re: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK >> (8gbps HBA) timeout question >> To: Justin Piszcz <jpis...@lucidpixels.com>, >> "veritas-bu@mailman.eng.auburn.edu" >> <veritas-bu@mailman.eng.auburn.edu> >> Message-ID: >> <cd1b62bc12595b478a5df26f7944ad0e077...@mercmbx11r.na.sas.com> >> Content-Type: text/plain; charset="us-ascii" >> >> Justin >> >> What os are you using. >> >> Which tape library? >> >> Which firmware level are you using in the lto-5. >> >> From: veritas-bu-boun...@mailman.eng.auburn.edu >> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin >> Piszcz >> Sent: Tuesday, April 10, 2012 8:16 AM >> To: veritas-bu@mailman.eng.auburn.edu >> Subject: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) >> timeout question >> >> 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. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20120410/cd6c3cb3/attachment-0001.htm >> >> ------------------------------ >> >> Message: 3 >> Date: Tue, 10 Apr 2012 08:36:11 -0400 >> From: "Justin Piszcz" <jpis...@lucidpixels.com> >> Subject: Re: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK >> (8gbps HBA) timeout question >> To: "'Len Boyle'" <len.bo...@sas.com>, >> <veritas-bu@mailman.eng.auburn.edu> >> Message-ID: <003301cd1716$83488620$89d99260$@lucidpixels.com> >> Content-Type: text/plain; charset="us-ascii" >> >> Hi, >> >> >> >> OS; RHEL 5.3 64-bit >> >> Tape Library (in all cases): SL500 w/FW 1432 >> >> LTO-5, I've tried them all that are available from Oracle (4), there is an >> issue with encryption on these drives in our setup, currently on BBN2. >> >> Due to the encryption bug (details below) had to stop using it for now, >> but >> we're seeing drives timing out as noted below with no encryption. >> >> >> >> I've tried A9Q5, B5BF, B6W2 and now on BBN2 (latest) >> >> >> >> -- >> >> >> >> Issue w/ encryption btw incase anyone is curious: >> >> It appears the IBM LTO-5 drive is advertising BOTH 12 and 60 bytes for the >> Maximum AUTH Key-associated data? >> But the IBM LTO-4 drive only advertises 12 bytes? >> >> $ grep 'Max AUTH Key-associtated data' lto4 >> Max AUTH Key-associtated data 12 (bytes) >> $ grep 'Max AUTH Key-associtated data' lto5 >> Max AUTH Key-associtated data 12 (bytes) >> Max AUTH Key-associtated data 60 (bytes) >> >> >> >> You can get the output via: >> >> /usr/openv/volmgr/bin/scsi_command -d /dev/nst0 -spi >> >> >> >> >From Oracle: >> >> The IBM LTO5 scsi reference manual does show that Maximum Authenticated >> Key-Associated Data (A-KAD) Bytes >> (000Ch) = 12 bytes >> >> >> >> Justin. >> >> >> >> From: Len Boyle [mailto:len.bo...@sas.com] >> Sent: Tuesday, April 10, 2012 8:19 AM >> To: Justin Piszcz; veritas-bu@mailman.eng.auburn.edu >> Subject: RE: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps >> HBA) timeout question >> >> >> >> Justin >> >> >> >> What os are you using. >> >> >> >> Which tape library? >> >> >> >> Which firmware level are you using in the lto-5. >> >> >> >> From: veritas-bu-boun...@mailman.eng.auburn.edu >> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin >> Piszcz >> Sent: Tuesday, April 10, 2012 8:16 AM >> To: veritas-bu@mailman.eng.auburn.edu >> Subject: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK (8gbps HBA) >> timeout question >> >> >> >> 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. >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20120410/e01c616e/attachment.htm >> >> ------------------------------ >> >> Message: 4 >> Date: Tue, 10 Apr 2012 08:42:47 -0700 >> From: nbuser <nbu...@live.com> >> Subject: Re: [Veritas-bu] IBM LTO-5 (8.0gbps FC) / QLogic 2562-CK >> (8gbps HBA) timeout question >> To: Justin Piszcz <jpis...@lucidpixels.com> >> Cc: veritas-bu@mailman.eng.auburn.edu >> Message-ID: <blu0-smtp1310ce9fb7e7fea01fb3127be...@phx.gbl> >> Content-Type: text/plain; charset="windows-1252" >> >> 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 >> <jpis...@lucidpixels.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@mailman.eng.auburn.edu >> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20120410/e83e54e5/attachment-0001.htm >> >> ------------------------------ >> >> _______________________________________________ >> Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> >> >> End of Veritas-bu Digest, Vol 72, Issue 7 >> ***************************************** > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu