From: Joe Scsi <joe.scsi@gmail.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: LUN discovery by SCSI midlayer?
Date: Tue, 15 Feb 2005 08:58:14 -0800 [thread overview]
Message-ID: <7526e3050502150858104f99eb@mail.gmail.com> (raw)
In-Reply-To: <20050215140642.GA2431@lists.us.dell.com>
> Can you take a look at the patches I posted last week and see if that
> would work for you?
Hmm, I'm not sure. The issue I have is that I know when target ports
appear and disappear, and I'd like to use some general SCSI midlayer
stuff to discover what LUNs are behind a target port. So if I have to
know the full HCTL then that doesn't really help me.
It seems kind of ugly if I have to do the REPORT_LUNs command
myself and manually call scsi_add_device() for each LUN.
(Disappearing target ports seem easier to handle, because I can keep
a list of LUNs per target port and call scsi_remove_device() on each LUN)
Thanks,
Joe
prev parent reply other threads:[~2005-02-15 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 4:35 LUN discovery by SCSI midlayer? Joe Scsi
2005-02-15 14:06 ` Matt Domsch
2005-02-15 16:58 ` Joe Scsi [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=7526e3050502150858104f99eb@mail.gmail.com \
--to=joe.scsi@gmail.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-scsi@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