From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Doug Gilbert <dougg@torque.net>
Subject: Re: Linux utility to determine WWN from a LUN number
Date: Fri, 14 Mar 2008 15:54:56 +0100 [thread overview]
Message-ID: <47DA91C0.4010106@suse.de> (raw)
In-Reply-To: <alpine.LRH.1.00.0803141025260.23740@bogart.boston.redhat.com>
Chip Coldwell wrote:
> On Fri, 14 Mar 2008, Hannes Reinecke wrote:
>> BTW: what is the main reason for scsitool?
>
> The main idea with scsitool is to be able to select, sort and output
> properties of SCSI disks. The properties it supports are
>
> --devname (sda, sdb, etc.)
> --hbtl (host:bus:target:lun nexus)
> --wwid
> --target-wwnn
> --target-wwpn
> --host-wwnn
> --host-wwpn
> --vendor
> --model
> --driver (e.g. lpfc, qla2xxx)
>
[ .. ]
>
Ah, I see. So basically combining lsscsi and scsi_id.
>> Does it have features which scsi_id and sg3_utils are missing?
>
> I think the answer, in a mathematical sense, is "no". However, I
> found it so cumbersome to combine the existing tools in scripts that
> it was worthwhile for me to write a new one from scratch. In
> addition, in deployments with thousands of LUNs, I think combining the
> existing tools in scripts can turn out to be rather slow.
>
So the logical choice would be to include scsitool in sg3_utils,
I believe. And scsi_id, too, for good measure. Just so that we're
on one page with generating unique identifiers for udev :-)
As already mentioned, I'm not especially partial as to _where_
scsi_id is kept. I'd happily move it over to sg3_utils.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2008-03-14 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 19:32 Linux utility to determine WWN from a LUN number lemons_terry
2008-03-13 20:39 ` Chip Coldwell
2008-03-13 21:43 ` malahal
2008-03-14 2:50 ` lemons_terry
2008-03-14 7:12 ` Hannes Reinecke
2008-03-14 14:24 ` Chip Coldwell
2008-03-14 21:10 ` lemons_terry
2008-03-14 13:57 ` Chip Coldwell
2008-03-14 14:03 ` Hannes Reinecke
2008-03-14 14:32 ` Chip Coldwell
2008-03-14 14:54 ` Hannes Reinecke [this message]
2008-03-14 15:34 ` Chip Coldwell
2008-03-14 15:37 ` Hannes Reinecke
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=47DA91C0.4010106@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=dougg@torque.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.