From: Jamie Wellnitz <Jamie.Wellnitz@emulex.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: rule for scsi tape changers? [u]
Date: Tue, 28 Aug 2007 13:41:42 +0000 [thread overview]
Message-ID: <20070828134142.GM8126@ma.emulex.com> (raw)
In-Reply-To: <200708280831.17841.aj@ciphirelabs.com>
Hi Andreas,
On Tue, Aug 28, 2007 at 08:31:17AM +0200, Andreas Jellinghaus [c] wrote:
> before re-inventing the wheel: does anyone have a rule for scsi device
> changers? the typical name would be /dev/changer and the devices are usualy
> sg* devices. kernel dmesg tells me:
> TID 513 Vendor: HP M Device: MSL6000 Seri Rev: 0507
> Vendor: HP Model: MSL6000 Series Rev: 0507
> Type: Medium Changer ANSI SCSI revision: 02
> 0:0:0:0: Attached scsi generic sg0 type 8
>
> udevinfo:
> BUS="scsi"
> ID="0:0:0:0"
> DRIVER="unknown"
> SYSFS{device_blocked}="0"
> SYSFS{iocounterbits}="32"
> SYSFS{iodone_cnt}="0x9f9"
> SYSFS{ioerr_cnt}="0xd"
> SYSFS{iorequest_cnt}="0x9f9"
> SYSFS{model}="MSL6000 Series "
> SYSFS{queue_depth}="1"
> SYSFS{queue_type}="none"
> SYSFS{rev}="0507"
> SYSFS{scsi_level}="3"
> SYSFS{state}="running"
> SYSFS{timeout}="0"
> SYSFS{type}="8"
> SYSFS{vendor}="HP "
>
> I see the rules on my ubuntu systems use ENV{ID_CDROM} and friends for cdrom
> devices. what creates these? is there a simialr ID_CHANGER information?
This rule, from the current udev git tree (it's been there for a
while, though):
# type 8 devices are "Medium Changers"
KERNEL="sg*", SUBSYSTEMS="scsi", ATTRS{type}="8", IMPORT{program}="scsi_id --export --whitelisted --fallback-to-sysfs -s %p -d $tempnode", SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}"
is intended to create a symlink in /dev/tape/by-id for changer
devices. It's in etc/udev/rules.d/60-persistent-storage.rules
>
> Thanks, Andreas
Thanks,
Jamie
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> 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
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
next prev parent reply other threads:[~2007-08-28 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 6:31 rule for scsi tape changers? [u] Andreas Jellinghaus [c]
2007-08-28 13:41 ` Jamie Wellnitz [this message]
2007-08-28 14:49 ` Kay Sievers
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=20070828134142.GM8126@ma.emulex.com \
--to=jamie.wellnitz@emulex.com \
--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).