From: "Roger Håkansson" <hson@ludd.luth.se>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Problems with multipathing
Date: Thu, 13 Apr 2006 19:14:54 +0200 [thread overview]
Message-ID: <443E870E.1070902@ludd.luth.se> (raw)
In-Reply-To: <443C19E6.8000607@ludd.luth.se>
Roger Håkansson wrote:
>
> With upstream I guess you mean 0.4.7 or "CVS-HEAD".
>
> Haven't tried that, but just looking at the requirements tells me I'll
> have a lot to do in order to even just to prepare to test it.
>
>> Dependencies :
>> Linux kernel
>>
>> * 2.6.10-rc*-udm2 or later
>> * 2.6.11-mm* or later
>> * 2.6.12-rc1 or later
>> udev 050+
>
> CentOS 4.3 have 2.6.9-34 and udev-039-10, and even though some stuff are
> backported I guess I have to update both and I can only imagine the
> amount of work that will render me, but I'll try to do it if I can find
> the time...
>
>
0.4.7 seems to work better without updating kernel or udev, but not
entirely...
Unless I've gotten this wrong, with pathgroupingpolicy set to failover I
should get two pathgroups where only one is active an if the active
fails, the other pathgroup will become active, correct?
Multibus pathgrouping will place all paths in the same pathgroup so that
all paths will share the I/O when they are active and if some path
fails, the I/O is spread among the active paths, correct?
Multibus works just like I expect it to, but failover doesn't fail the
path entirely.
This is what 'multipath -ll' gives me after I have disconnected one HBA
from the fabric.
mpath1 (3600d0230000000000b0191489a946602)
[size=183 GB][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:1:1 sdc 8:32 [active][faulty]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:0:1 sdf 8:80 [active][ready]
mpath2 (3600d0230000000000b0191489a946600)
[size=97 GB][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 1:0:1:0 sdb 8:16 [failed][faulty]
\_ 2:0:0:0 sde 8:64 [active][ready]
Notice that sdc is faulty, but still active and both pathgroups are
enabled but none is active...
I've noticed this problem when I/O is active ( I was running a 'dd
if=/dev/zero of=/mount_point count=10000000000' to each mpath) when one
"path" fails, if there is no activity at all the failover works.
next prev parent reply other threads:[~2006-04-13 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 18:10 Problems with multipathing Roger Håkansson
2006-04-11 18:42 ` Christophe Varoqui
2006-04-11 21:04 ` Roger Håkansson
2006-04-13 17:14 ` Roger Håkansson [this message]
2006-04-13 20:48 ` Christophe Varoqui
2006-04-16 22:44 ` Roger Håkansson
2006-04-17 0:35 ` Roger Håkansson
2006-04-17 9:43 ` Christophe Varoqui
2006-04-17 14:17 ` Roger Håkansson
2006-04-18 4:47 ` Christophe Varoqui
2006-04-18 5:04 ` Roger Håkansson
2006-04-18 19:38 ` James Smart
2006-04-18 19:24 ` James Smart
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=443E870E.1070902@ludd.luth.se \
--to=hson@ludd.luth.se \
--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.