Networker

Re: [Networker] Linux Tape Drive Re-Ordering Issue

2010-11-03 17:14:03
Subject: Re: [Networker] Linux Tape Drive Re-Ordering Issue
From: Chester Martin <cmartin AT SPP DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 3 Nov 2010 16:11:13 -0500
We had that issue when we first put our environment into production.  Our 
problem ended up being we were using Emulex cards.  Once we replaced them with 
qlogic cards the problems went away.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Brian Narkinsky
Sent: Wednesday, November 03, 2010 3:26 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Linux Tape Drive Re-Ordering Issue

I had the same thing with an ESN.  I know that UDEV has be a certain level for 
persistent binding to work.  The version I upgraded to was SLES 9 udev 
-021-36.69.i586.rpm.

Brian

On Wed, Nov 3, 2010 at 4:17 PM, Mark Leese <mark.r.leese AT gmail DOT com> 
wrote:

> Hi Raymond,
>
> It is indeed an issue with the udev environment within Linux, I had a 
> similar problem with some EMC EDL/CDL boxes. These have an Embedded 
> Storage Node facility that run Linux. On a customer that I have been 
> working at we recently upgraded the firmware and as a matter of course 
> the Linux installation and we discovered a bug with the implementation 
> of udev. Every reboot, even when using persistent binding 
> (/dev/tape/by-id/xxxxxxx-nst) would have problems, once we added the udev 
> patches everything worked fine.
>
> I don't have a link to the exact problem however there is a solution 
> on powerlink that goes into to the problem. Incidentally the flavour 
> of Linux was SuSE/Novell, so the tech support section on their website 
> may also provide information to help resolve your issue.
>
> Thanks,
>
> Mark.
>
> On 3 November 2010 19:07, Davis, Raymond P <  
> Raymond.P.Davis AT questdiagnostics DOT com> wrote:
>
> >
> >  Hi,
> >
> >  We have a Quantum LTO Tape library with a bunch of drives. Our 
> > Linux networker server sees one of the partitions. We have just 
> > finally implemented persistent binding on the Linux host and things 
> > are working better. Before that, we needed to reconfigure the tape 
> > library with every Linux reboot. The next issue seems to be when a 
> > tape drive goes awry, it loses its drive mapping and issues a SCSI 
> > reset, which in turn reorders the tape drives dynamically. Has 
> > anyone else had this experience and are there any ideas as to how to 
> > circumvent this problem.
> >
> >
> > I have reached out internally to my Linux group who are looking into it.
> > I asked Quantum and they know about it but don't have any solution 
> > for me as of yet. Finally, EMC says it's a Linux issue and not 
> > specific to networker. BTW, when this happens, we wind up needing to 
> > bring down 3 separate netwoker environments and 3 library 
> > partitions, hard booting the library and rebooting the Linux networker 
> > server/ storage node.
> >
> > Thanks for any help.
> >
> >
> > Raymond Davis
> >
> > Quest Diagnostics | Sr. Storage Engineer | 1200 Wall St West | 
> > Lyndhurst, NJ 07071  USA | phone +1.201.729.7882 |  mobile
> > +1.201.841.2335 | Raymond.P.Davis AT QuestDiagnostics DOT com |
> > www.QuestDiagnostics.com <http://www.questdiagnostics.com/>
> >
> > Please think about resource conservation before you print this 
> > message
> >
> >
> > ------------------------------------------
> > The contents of this message, together with any attachments, are 
> > intended only for the use of the person(s) to which they are 
> > addressed and may contain confidential and/or privileged 
> > information. Further, any medical information herein is confidential 
> > and protected by law. It is unlawful for unauthorized persons to 
> > use, review, copy, disclose, or disseminate confidential medical 
> > information. If you are not the intended recipient, immediately 
> > advise the sender and delete this message and any attachments. Any 
> > distribution, or copying of this message, or any attachment, is 
> > prohibited.
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu 
> > and
> type
> > "signoff networker" in the body of the email. Please write to 
> > networker-request AT listserv.temple DOT edu if you have any problems with 
> > this list. You can access the archives at 
> > http://listserv.temple.edu/archives/networker.html or via RSS at 
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or via RSS at 
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or via RSS at 
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER