From: Kurt Garloff <kurt@garloff.de>
To: Shobhit Mathur <shobhitmmathur@yahoo.com>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: SCSI-ID persistence query...
Date: Wed, 19 May 2004 22:20:45 +0200 [thread overview]
Message-ID: <20040519202045.GA367@tpkurt.garloff.de> (raw)
In-Reply-To: <20040513110021.36867.qmail@web51006.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On Thu, May 13, 2004 at 04:00:21AM -0700, Shobhit Mathur wrote:
> Hello,
>
> I have a few basic questions pertaining to SCSI-id
> numbering & persistence :
>
> * How do SCSI targets/LUNs get numbered ? My view is
> that the OS numbers them as it receives cmd-response.
> * If the above observation is correct, a disk with a
> particular id during one boot, will not have the same
> id during the next boot, which can have other
> consequences...
>
> My question is: How is SCSI numbering done and how is
> it persistent across boots ?
It's not persistent by default.
The SCSI devices are just enumerated in the order of detection.
If you look for more persistent device name for 2.4 and 2.6, have a
look at scsidev.
For 2.6, another option is to have your hotplug scripts call udev
call scsi_id.
Regards,
--
Kurt Garloff <kurt@garloff.de> [Koeln, DE]
Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL]
Linux: SUSE Labs (Head) <garloff@suse.de> [SUSE Nuernberg, DE]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-19 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 11:00 SCSI-ID persistence query Shobhit Mathur
2004-05-13 16:00 ` Bryan Henderson
2004-05-19 20:20 ` Kurt Garloff [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 11:42 Parthiban Manickam - NPD, Chennai
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=20040519202045.GA367@tpkurt.garloff.de \
--to=kurt@garloff.de \
--cc=linux-scsi@vger.kernel.org \
--cc=shobhitmmathur@yahoo.com \
/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