From: Andries.Brouwer@cwi.nl
To: garloff@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/scsi/map
Date: Sat, 15 Jun 2002 18:04:19 +0200 (MEST) [thread overview]
Message-ID: <UTC200206151604.g5FG4JQ26968.aeb@smtp.cwi.nl> (raw)
> How can one assign stable device names to SCSI devices in
> case there are devices that may or may not be switched on or connected.
An interesting unsolved problem.
[Your discussion confuses a few things, especially in the context
of removable devices: a uuid lives on the disk, the C,B,T,U tends
to identify the drive rather than the disk.]
> Life would be easier if the scsi subsystem would just report which
> SCSI device (uniquely identified by the controller,bus,target,unit tuple)
> belongs to which high-level device.
Yes. I took your patch, ported it to 2.5, and tried it out.
# cat /proc/scsi/map
# C,B,T,U Type onl sg_nm sg_dev nm dev(hex)
1,0,06,00 0x00 1 sg0 c:15:00 sda b:08:00
2,0,00,00 0x00 1 sg1 c:15:01 sdb b:08:10
2,0,00,01 0x00 1 sg2 c:15:02 sdc b:08:20
3,0,00,00 0x00 1 sg3 c:15:03 sdd b:08:30
3,0,00,01 0x00 1 sg4 c:15:04 sde b:08:40
Very good - in combination with /proc/scsi/scsi this gives
good information. I like it.
But just "cat /proc/scsi/map" is not good enough.
>From the above output alone one cannot easily guess which is which.
One would need a small utility that reads /proc/scsi/map and
/proc/scsi/scsi and produces something readable.
Will add sth to util-linux in case this gets accepted.
Andries
next reply other threads:[~2002-06-15 16:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 16:04 Andries.Brouwer [this message]
2002-06-16 21:04 ` /proc/scsi/map Kurt Garloff
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 20:06 /proc/scsi/map Chris Adams
2002-06-18 20:25 ` /proc/scsi/map Andreas Dilger
2002-06-17 12:55 /proc/scsi/map Heinz, Michael
2002-06-16 15:59 /proc/scsi/map Borsenkow Andrej
2002-06-15 23:00 /proc/scsi/map Andries.Brouwer
2002-06-15 21:54 /proc/scsi/map Andries.Brouwer
2002-06-15 22:27 ` /proc/scsi/map Douglas Gilbert
2002-06-15 22:40 ` /proc/scsi/map Sancho Dauskardt
2002-06-16 20:36 ` /proc/scsi/map Kurt Garloff
2002-06-15 22:28 ` /proc/scsi/map Sancho Dauskardt
2002-06-15 21:08 /proc/scsi/map Douglas Gilbert
[not found] <garloff@suse.de>
2002-06-15 13:36 ` /proc/scsi/map Kurt Garloff
2002-06-15 14:08 ` /proc/scsi/map John Summerfield
2002-06-17 11:33 ` /proc/scsi/map Kurt Garloff
2002-06-15 15:52 ` /proc/scsi/map Richard Gooch
2002-06-16 19:41 ` /proc/scsi/map Kurt Garloff
2002-06-17 17:49 ` /proc/scsi/map Ingo Oeser
2002-06-15 19:49 ` /proc/scsi/map Sancho Dauskardt
2002-06-16 19:24 ` /proc/scsi/map Albert D. Cahalan
2002-06-16 21:22 ` /proc/scsi/map Kurt Garloff
2002-06-17 20:35 ` /proc/scsi/map Patrick Mansfield
2002-06-17 20:57 ` /proc/scsi/map Kurt Garloff
2002-06-17 21:47 ` /proc/scsi/map Patrick Mansfield
2002-06-17 22:08 ` /proc/scsi/map Doug Ledford
2002-06-17 23:06 ` /proc/scsi/map Kurt Garloff
2002-06-18 2:40 ` /proc/scsi/map Doug Ledford
2002-06-18 4:32 ` /proc/scsi/map Douglas Gilbert
2002-06-18 5:12 ` /proc/scsi/map Doug Ledford
2002-06-18 9:03 ` /proc/scsi/map Kurt Garloff
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=UTC200206151604.g5FG4JQ26968.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=garloff@suse.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®