linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fw: tape implementation question for SLES9 and persistent Binding
Date: Thu, 27 Oct 2005 11:50:33 +0000	[thread overview]
Message-ID: <4360BF09.2050108@suse.de> (raw)
In-Reply-To: <OF4BADA02D.3551B7C8-ONC12570A6.006EA080-C12570A6.006EBD1B@de.ibm.com>

Stefan Neff wrote:
> Hi linux-hotplug-devels,
> 
> found on several internet web pages your email. I was looking for
> implementation help for persistant binding of tape via udev-command under
> SLES9 on a IBM pSerie with EMULEX LP10.000
> 
Ah, yes. Up to know we hadn't considered that someone would need
persistent device names for tapes.

> The problem I / we is that we dont't realy understand all the theoretic
> explamantion about the udev. All provided examples only talk about printer
> and disk - not tape.
> With disk and printeres it looks easy ... because for printers in the
> "sysfs" is the s/n listed and for disk you can see the ID. With Tapes its
> not the case - in the "sysfs" there is no S/N nor the WWNN or WWPN. So you
> dont get information for a unique assignment from there.
>
Well, yes. But as (thankfully) most tapes are SCSI tapes anyway (or at
least connected via a SCSI bridge) we can use the SCSI information.

This is not really a problem. The main problem is that each tapes comes
in different flavours. It has two modi (rewind and non-rewind) and
several configurations, four of which are supported by Linux (that's
what the 'a', 'l', or 'm' is about).
To make matters even worse, all configurations (apart from the default
one) have to be configured _explicitely_ otherwise they simply won't work.

So, as to not confuse users even more I've got the following suggestion:

tape/by-path/pci-0000:d8:01.0-scsi-1:0:0:0-st
tape/by-path/pci-0000:d8:01.0-scsi-1:0:0:0-sta
tape/by-path/pci-0000:d8:01.0-scsi-1:0:0:0-stl
tape/by-path/pci-0000:d8:01.0-scsi-1:0:0:0-stm

for the rewinding tapes; for non-rewinding add a 'n' in front of 'stX'.
And if the tape supports SCSI EVPD pages we might even get a 'by-id'
symlink like

tape/by-id/200e09e600002d683-st
...

If the tape doesn't support SCSI EVPD pages 0x80 or 0x83 then we'll have
a hard time distinguishing between two tapes with the same make; hence
the 'by-id' symlink won't be available there.

D'accord?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      reply	other threads:[~2005-10-27 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 20:10 Fw: tape implementation question for SLES9 and persistent Binding Stefan Neff
2005-10-27 11:50 ` Hannes Reinecke [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4360BF09.2050108@suse.de \
    --to=hare@suse.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).