All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: DS4000 with multipath-tools 0.4.5
Date: Thu, 18 Jan 2007 08:05:38 +0100	[thread overview]
Message-ID: <45AF1C42.8050304@suse.de> (raw)
In-Reply-To: <OF396F7E56.FA311C77-ON85257261.00787002-85257261.00789A54@mohegansun.com>

TGrozev@mohegansun.com wrote:
> I compiled it, and it's working good. The only thing is, when I query the 
> priority of a drive, I'm getting "Auto-volume Transfer not enabled":
> 
> ---
> # ./mpath_prio_tpc /dev/sdc
> Auto-volume Transfer not enabled6
> 
> # ./mpath_prio_tpc /dev/sdd
> Auto-volume Transfer not enabled1
> ---
> 
> I seem to be getting 6 for my preferred path and 1 for standby, which is 
> good. Is AVT required, or can I still use mpath_prio_tcp?
> I have multiple nodes of a Linux Cluster accessing the LUNs, so AVT has to 
> be disabled.
> 
Unfortunately the current multipath-tools do not handle RDAC mode.
You'll need a specific hardware handler to do this properly.
Mike Christie once did some work on it, but I'm not sure if it made it
into RHEL. We will be adding support for it for SLES10 SP1, so you might
get lucky with that.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de

  reply	other threads:[~2007-01-18  7:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10 23:08 [RFC PATCH 3/3] blk_end_request: caller change Kiyoshi Ueda
2007-01-10 23:08 ` Kiyoshi Ueda
2007-01-11  8:34 ` Jens Axboe
2007-01-11 14:28   ` DS4000 with multipath-tools 0.4.5 TGrozev
2007-01-12 21:01     ` Benjamin Marzinski
2007-01-12 21:57       ` TGrozev
2007-01-18  7:05         ` Hannes Reinecke [this message]
2007-01-18  9:28           ` Yury Konovalov
2007-01-11 17:01   ` [RFC PATCH 3/3] blk_end_request: caller change Kiyoshi Ueda
2007-01-11 17:01     ` Kiyoshi Ueda

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=45AF1C42.8050304@suse.de \
    --to=hare@suse.de \
    --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.