From: Brian Waite <waite@skycomputers.com>
To: Bill Davidsen <davidsen@tmr.com>, Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFC] [PATCH] 0/7 2.5.35 SCSI multi-path
Date: Thu, 19 Sep 2002 17:29:24 -0400 [thread overview]
Message-ID: <200209191729.24069.waite@skycomputers.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020919171118.24603A-100000@gatekeeper.tmr.com>
This is why we had to make another abstraction layer that was the "uniqueness
driver" This allowed the admin to configure a device without seial numbers to
be multipathed if they knew it was multipathed by explicitly specifing the
host bus, target, lun of all the paths to a speciic device. We never got the
chance to develop an intellegent way a determining multipathed-ness so we
left it to the user. Not ideal but it worked for our customer. I would like
to think there is a better way to determind uniqueness, but the nice thing
was we made the uniquness driver a module that could be replaced, thus
letting us develop new uniqueness algorithms in the future. I think the
concept is good, maybe not the implimentation. It also allows you to say you
don't like how we do... well you know the rest
Thanks
Brian
On Thursday 19 September 2002 5:16 pm, Bill Davidsen wrote:
> On Wed, 18 Sep 2002, Patrick Mansfield wrote:
> > Devices without serial numbers are treated as if they had different
> > serial numbers, they show up as if there was no multi-path support.
>
> That doesn't solve the problem, does it? If you have two devices w/o
> serial they could look like one with multipath, with the change you note
> that is prevented by making a single multipath device w/o serial look like
> two. I have visions of programs using /dev/st0 and /dev/st1, having used
> backup programs which grabbed every drive with a tape ready.
>
> It is indeed a messy problem.
prev parent reply other threads:[~2002-09-19 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 22:49 [RFC] [PATCH] 0/7 2.5.35 SCSI multi-path Patrick Mansfield
2002-09-17 22:50 ` [RFC] [PATCH] 1/7 " Patrick Mansfield
2002-09-17 22:50 ` [RFC] [PATCH] 2/7 " Patrick Mansfield
2002-09-17 22:51 ` [RFC] [PATCH] 3/7 " Patrick Mansfield
2002-09-17 22:52 ` [RFC] [PATCH] 4/7 " Patrick Mansfield
2002-09-17 22:52 ` [RFC] [PATCH] 5/7 " Patrick Mansfield
2002-09-17 22:53 ` [RFC] [PATCH] 6/7 " Patrick Mansfield
2002-09-17 22:54 ` [RFC] [PATCH] 7/7 " Patrick Mansfield
2002-09-18 15:17 ` [RFC] [PATCH] 0/7 " Brian Waite
2002-09-18 16:08 ` Patrick Mansfield
2002-09-19 21:16 ` Bill Davidsen
2002-09-19 21:29 ` Brian Waite [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=200209191729.24069.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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;
as well as URLs for NNTP newsgroup(s).