From: Evan Felix <evan.felix@pnl.gov>
To: christophe varoqui <christophe.varoqui@free.fr>
Cc: linux-scsi@vger.kernel.org
Subject: Re: HSV : ghosts & multipath
Date: Tue, 12 Aug 2003 09:23:47 -0700 [thread overview]
Message-ID: <1060705427.5188.16.camel@e-linux> (raw)
In-Reply-To: <3F3820C9.4060004@free.fr>
Doh!.. i forgot to answer your second question:
On Mon, 2003-08-11 at 16:03, christophe varoqui wrote:
> More generally, how do you manage access to your HSV LUNs ? I personnaly
> would hate to use SecurePath which locks the user to one distribution
> and has not passed the "community peer-review test". Any alternative
> applicable in a dual fabric, dual attached hosts & controlers (4
> paths/host including 2 ghosts : 2 paths through the left fabric, 2 paths
> through the right) ?
>
I Do not have a full solution yet, but the things we have looked at are:
1. Qlogic 2300 failover driver, which did seem to work fairly well when
you have two active paths. does not understand the ghost issues at all.
2. The linux md multipath driver works fairly reliable, but also does
not understand ghost devices.
3. Do nothing. This is actually what we are doing now, as we
investigate the other options. In a failure situation the plan is to
re-load the qlogic modules, re-run scsidev which will remap the failed
disks to the correct position.
I am still waiting on a usuable version of SecurePath for IA64, and have
not seen even the beta yet.... since HP is supporting our box we may be
able to get more access to the code and have them tailor a version for
our specific kernel and software config. Maybe.
Hope that helps.
Evan
prev parent reply other threads:[~2003-08-12 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 23:03 HSV : ghosts & multipath christophe varoqui
2003-08-12 15:52 ` Evan Felix
2003-08-13 11:53 ` christophe.varoqui
2003-08-12 16:23 ` Evan Felix [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=1060705427.5188.16.camel@e-linux \
--to=evan.felix@pnl.gov \
--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