From: christophe varoqui <christophe.varoqui@free.fr>
To: evan.felix@pnl.gov
Cc: linux-scsi@vger.kernel.org
Subject: HSV : ghosts & multipath
Date: Tue, 12 Aug 2003 01:03:37 +0200 [thread overview]
Message-ID: <3F3820C9.4060004@free.fr> (raw)
Hello,
I read your contribution to scsidev, regarding HSV.
You seem to have an intimate knowledge of these controlers.
Do you happen to have a clue on how to force the activation of a ghost
LUN from a Linux host ?
The rationale being : in a multipath config, when all active path are
exhausted you should be able to activate the ghosts paths rather than
let the device die.
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) ?
next reply other threads:[~2003-08-11 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 23:03 christophe varoqui [this message]
2003-08-12 15:52 ` HSV : ghosts & multipath Evan Felix
2003-08-13 11:53 ` christophe.varoqui
2003-08-12 16:23 ` Evan Felix
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=3F3820C9.4060004@free.fr \
--to=christophe.varoqui@free.fr \
--cc=evan.felix@pnl.gov \
--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