Dean:
The reason why your commands below aren't working properly is that
you're making the same mistake I did. The writers of the udev supporting
utilities (scsi_id, etc.) decided that since their software would only work
against the devices in the /sys directory, that they would ignore the /sys
directory. So, your commands should be:
scsi_id -u -g -s /class/scsi_tape/nst0
Or
scsi_id -u -g -s $(udevinfo -q path -n /dev/nst0)
Try those and see if you get better information.
However, the devices you want to use should be in /dev/tape/by-id/*. In RHEL
5.1, they don't show up there due to a now patched race condition within udev.
The udev rules were written wrong, too, but at least they'd pick up the first
10 tape drives on your system.
Like Terry said, in RHEL 5.3 they show up better, but with a caveat:
In some of our older CDLs (we have 2 EDL 4200s with v3.1 and 1 CDL 310 with
v2.2 code, I am specifically referring to the latter in this case) the tape
drives' serial numbers come through with the same number, so our symlinks in
/dev/tape/by-id/ get overwritten by the next one down the chain. So, on this
one, I'm working to find some sort of drive specific information to use in my
own custom udev rules. I hope you're using something more recent.
For more information on writing your own udev rules (and an understanding of
the subsystem in general), I found this document to be helpful:
http://reactivated.net/writing_udev_rules.html
Sean
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Eidler, Dean
Sent: Tuesday, March 24, 2009 10:35 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Persistent Binding in Linux
NW 7.3.4
RH Linux Enterprise 5, v2.6 kernel.
I (a *nix newbie) am trying to setup persistent binding on a Linux host
connecting to EMC Clarion Virtual Tape Library (requested by EMC).
Before I setup the udev rules I need to get the "name" of the tape
devices. I have tried
Scsi_id -u -g -s /sys/class/scsi_tape/nst0 and get nothing back.
I have also tried
Scsi_id -u -g -s /dev/nst0 and get nothing back.
What is the correct device name to use as an argument to scsi_id? Local
networker support has refused to help.
Thanks
Dean.
=======================================================================
Attention: The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the
sender immediately.
=======================================================================
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
|
