Networker

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

2010-11-05 08:30:33
Subject: Re: [Networker] Linux Tape Drive Re-Ordering Issue
From: Matthew Huff <mhuff AT OX DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 5 Nov 2010 08:29:18 -0400
I'm not sure you understand persistent binding. With persistent binding, no 
changes (including SCSI bus resets) will change the names (and therefore the 
drive order).



-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Davis, Raymond P
Sent: Friday, November 05, 2010 8:25 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Linux Tape Drive Re-Ordering Issue

Thanks Terry,

As I said, the persistent binding is working with our Rhat Linux
Networker server and storage nodes,,, at boot up. The issue is when a
tape drive goes bad during normal operations. When this happens,
sometimes, and I not sure what the occasion is, a SCSI Bus reset is
done, which in turn causes the tape drive reordering. 

This causes a major disruption and needs a lot of subsequent work to
recover. I'm trying to get a handle on how to 'catch' when a drive goes
bad and avoid the SCSI scan reset. If there is a way to not lose the
pathing of a failed drive, then I'd be set.

Thoughts?


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 

Please think about resource conservation before you print this message

 


-----Original Message-----
From: terry.lemons AT emc DOT com [mailto:terry.lemons AT emc DOT com] 
Sent: Thursday, November 04, 2010 09:49 AM
To: Davis, Raymond P
Cc: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: RE: [Networker] Linux Tape Drive Re-Ordering Issue

Hi Raymond

You didn't mention which Linux distribution you are using.  If it is one
of the Big Ones, then NetWorker will work with that distribution's
persistently-named device special files (which are, in fact, symbolic
links to the actual device files).  These are usually created in a
directory like /dev/tape/by-id/.

As of around NetWorker V7.5 (don't remember the actual release offhand),
you can enable NetWorker's use of persistently-named device files by
setting the NetWorker storage node resource in Properties -> Device
Management -> Use Persistent Names.  Note that this works only on most
Linux distributions and on Windows; other operating systems are not
supported, to my knowledge.  If you want to use this feature, first set
it in the storage node resource, then scan for devices (in NMC) or use
the CLI 'inquire' command. You'll notice that the persistently-named
devices are now displayed.  Com0plete the configuration using those
devices.  See the Networker Administration Guide for more information.

The udev in use in earlier Linux distributions had awful bugs related to
persistent naming.  In my experience, this began working in SLES 9 SP3,
SLES 10 SP1 and in RHEL 4.7 and RHEL 5.3 (see
http://kbase.redhat.com/faq/docs/DOC-4202).

Hope this helps.
tl


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


 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

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

------------------------------------------
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