Have you tested what happens when a tape drive fails and you have to replace it 
with a new one
(which has a different serial number) doing it that way?

For those of us that created our jukebox back in the 7.2 (or earlier) days and 
have the jukebox
defined using the rd=<storagenode>:/dev/nstX devices, I strongly urge you to 
consider coercing
udev into picking which /dev/nstX device the drive is based on the serial 
number (then
remembering to update that rule when you replace a drive).

I have set it up as /etc/udev/rules.d/20-local.rules -- which is a copy of the 
50-udev.rules
file with a line added for each tape drive like:

KERNEL=="nst[0-9]*", SUBSYSTEM=="scsi_tape", 
ENV{ID_SERIAL}=="3500507631203e5d4", NAME="nst0",
SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}-nst", SYMLINK+="tape0"

just in front of the

KERNEL=="nst[0-9]*", SUBSYSTEM=="scsi_tape", ENV{ID_SERIAL}=="?*",
SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}-nst"

line.

Why would I do something this convoluted?  Because I don't like the risk of 
having to perform a
25 hour jukebox inventory just because a tape drive failed and suddenly I have 
to re-define the
jukebox because EMC's code messed up and can't figure out what happened to that 
tape drive that
broke and was removed.

Frank

On 11/5/10 8:43 AM, Riku Valli wrote:
> Matthew Huff wrote:
>> 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).
>>   
> Yes, tape drives uses serialnumbers for devicenames at RHEL 5 for persistent 
> bindings. So them
> cannot change.
> /dev/tape/by-id/scsi-3500308c09fb49000-nst
> 
> When you made jukebox, you should select use persistent names and NMC:s 
> graphical gui uses
> automatic this by-id name convention or manual with command jbconfig -p, but 
> jbconfig is'nt
> recommed to use at newer Networker versions.

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