From: Jedi/Sector One <lvm@pureftpd.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Multipath without round-robin?
Date: Thu, 10 Jun 2004 22:32:47 +0159 [thread overview]
Message-ID: <20040610203309.GA18186@c9x.org> (raw)
Hello.
I'm trying to get multipath working with LVM2 (2.6.7-rc2-udm2 kernel) with
an LSI storage array.
The array has two FC controllers, HBAs are two identical Qlogic 2340.
On the array, "preferred" controllers are assigned to each LUN.
Unfortunately, it looks like dm-multipath always does round-robin load
balancing.
The result is that the array fills up the (SANtricity) error log with
messages like "LUN was accessed through the wrong controller".
Is there any way to keep failover abilities without load balancing?
Best regards,
-Frank.
next reply other threads:[~2004-06-10 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 20:33 Jedi/Sector One [this message]
2004-06-10 21:34 ` [linux-lvm] Multipath without round-robin? Chris Croswhite
2004-06-10 22:06 ` Austin Gonyou
2004-06-10 22:10 ` Austin Gonyou
2004-06-10 22:32 ` Jedi/Sector One
2004-06-11 20:06 ` Mike Christie
2004-06-11 21:02 ` Chris Croswhite
2004-06-11 21:34 ` Mike Christie
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=20040610203309.GA18186@c9x.org \
--to=lvm@pureftpd.org \
--cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox