From: Patrick Mansfield <patmans@us.ibm.com>
To: christophe varoqui <christophe.varoqui@free.fr>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: storageworks controlers & linux-scsi
Date: Thu, 28 Aug 2003 13:06:26 -0700 [thread overview]
Message-ID: <20030828130626.A15749@beaverton.ibm.com> (raw)
In-Reply-To: <20030828013706.45760cb5.christophe.varoqui@free.fr>; from christophe.varoqui@free.fr on Thu, Aug 28, 2003 at 01:37:06AM +0200
On Thu, Aug 28, 2003 at 01:37:06AM +0200, christophe varoqui wrote:
>
> I leave for a 2 week vacation, but if the HSV LUNs handling is turned to a usable state I'll be able to post a GPL C agent to handle DM multipath autoconfig & reconfig on event (through VPD 0x83 for wwid detection and TUR for ghosts detection) in about 3 weeks. In hope there will interest to move it to a broader use.
>
Hi -
Is that a 2.4 solution?
I was starting to work on a hotplug interface to get and store scsi wwid's
or serial numbers for use with 2.6.
We need a method that would (ideally) work for all users, so we: don't
hang broken devices, can use other pages (0x80), can use vendor
specific methods, and works for udev or multipath config tools.
We need a black/white list (or config file) for the broken or special
devices.
Have you seen the libsysfs/udev code? We can use libsysfs for common
interfaces to get/set a scsi serial number, and for other common uses of
sysfs such as getting the bus_id, or figuring out if we have a scsi
device.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-08-28 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 12:55 storageworks controlers & linux-scsi christophe.varoqui
2003-08-27 15:56 ` James Bottomley
2003-08-27 23:37 ` christophe varoqui
2003-08-28 20:06 ` Patrick Mansfield [this message]
2003-08-29 10:25 ` christophe.varoqui
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=20030828130626.A15749@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=christophe.varoqui@free.fr \
--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