From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools and queue-length/service-time path selectors oops
Date: Tue, 15 Sep 2009 11:10:29 +0900 [thread overview]
Message-ID: <4AAEF795.9060301@ct.jp.nec.com> (raw)
In-Reply-To: <20090914151251.GA17421@thumper2>
Hi Andy,
On 09/15/2009 12:12 AM +0900, Andy wrote:
> On Mon, Sep 14, 2009 at 11:15:47AM +0900, Kiyoshi Ueda wrote:
>> Hi Andy,
>>
>> Thank you for reporting this.
>>
>> On 2009/09/12 6:34 +0900, Andy wrote:
>>> When I try to change the path selector in multipath.conf to queue-length or
>>> service-time I get a kernel oops.
>> I'd like to see the information of your environment, so could you
>> give me the followings?
>
> This is a test system, so there is no problem try things out on it.
>
> version information:
>
> Distribution : Debian squeeze/sid
> kernel: 2.6.31
>
> multipath-tools v0.4.9 (04/04, 2009)
>
> dmsetup --version
> Library version: 1.02.36 (2009-08-06)
> Driver version: 4.15.0
>
>
> multipath.conf part:
>
> multipath {
> wwid 350002ac000020246
> path_grouping_policy multibus
> # path_selector "round-robin 0"
> path_selector "queue-length"
> rr_min_io 8 # u02 io count
> alias u02
> }
OK, thanks.
Please specify the path_selector part in the same way as
round-robin like below:
path_selector "queue-length 0"
Note that '0' is the required argument which specifies the number
of path_selector parameters.
I think this is a bug in the parameter parsing of multipath target
driver, not queue-length/service-time specific.
Thanks,
Kiyoshi Ueda
next prev parent reply other threads:[~2009-09-15 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 21:34 multipath-tools and queue-length/service-time path selectors oops Andy
2009-09-14 2:15 ` Kiyoshi Ueda
2009-09-14 15:12 ` Andy
2009-09-15 2:10 ` Kiyoshi Ueda [this message]
2009-09-15 14:35 ` Andy
2009-09-18 1:37 ` Kiyoshi Ueda
[not found] ` <20090924192859.GA14887@thumper2>
2009-09-28 7:41 ` 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=4AAEF795.9060301@ct.jp.nec.com \
--to=k-ueda@ct.jp.nec.com \
--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.