From: Christophe Varoqui <christophe.varoqui@free.fr>
To: dm-devel@redhat.com
Subject: Re: Experiences with multipath-tools and EMC CLARiiON
Date: Thu, 10 Feb 2005 10:11:59 +0100 [thread overview]
Message-ID: <420B255F.8000100@free.fr> (raw)
In-Reply-To: <200502091314.56085.tore@linpro.no>
Tore Anderson wrote:
> Host-based failover doesn't seem to work, or at least I cannot figure
> out how to do it. "sg_start -s /dev/sdb 1" gives me this:
>
> sync_cache: SCSI status: Check Condition
> Fixed format, current; Sense key: Not Ready
> Additional sense: Logical unit not ready, manual intervention required
>
> I guess the "tresspass" command is a proprietary thing and what is
> needed is just a userspace utility that is able to send the same thing
> down the fibre as the dm-emc kernel module is.
>
>
>
Yes, "sg_start -s /dev/sdb 1" is not an adequate mean to force a
host-driven failover for the clariion hardware. You need the trespass
tool included in recent sg3_utils package.
For the rest, I guess Lars will be able to give you more feedback.
> Cristophe: Should I make a summary of this email and add it to your
> TestedEnvironments page? I'm not sure if I could've made it work by
> configuring multipathd in another way (for instance the numbers on the
> hardware_handler line I just found in some mailing list archive, I have
> no idea what they mean) - so I'm a bit afraid of ending up updating it
> with flat-out incorrect information.
>
>
>
We'll do that as soon as Lars has helped you refining your config.
Regards,
cvaroqui
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2005-02-10 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 12:14 Experiences with multipath-tools and EMC CLARiiON Tore Anderson
2005-02-10 9:11 ` Christophe Varoqui [this message]
2005-02-10 9:46 ` Tore Anderson
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=420B255F.8000100@free.fr \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.