From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christophe BOULLANGER <cbo@info-services.biz>
Subject: Re: Multipath conf
Date: Tue, 14 Jun 2011 15:12:37 +0100 [thread overview]
Message-ID: <4DF76C55.4070802@redhat.com> (raw)
In-Reply-To: <80B8E0EA896B3E489A5802234274BA9C77C968B828@sandy.IS972DH.com>
On 06/10/2011 03:46 PM, Christophe BOULLANGER wrote:
> Hi,
> i wanna know what is that difference of both stout of multipath -ll
> <Anti-T> multipath -ll
> <Anti-T> mpath2 (350010b900004b868) dm-3 IBM-ESXS,GNA073C3ESTT0Z
> <Anti-T> [size=68G][features=0][hwhandler=0]
> <Anti-T> \_ round-robin 0 [prio=1][active]
> <Anti-T> \_ 1:0:1:0 sdc 8:32 [active][ready]
> <Anti-T> \_ round-robin 0 [prio=1][enabled]
> <Anti-T> \_ 1:0:3:0 sde 8:64 [active][ready]
> <Anti-T> c quoi la diff entre ca
> <Anti-T> et ca
> <Anti-T> orasm (36005076b0755627f4dee6fd70000002d) dm-6 IBM,1820N00
> <Anti-T> size=250G features='1 queue_if_no_path' hwhandler='0' wp=rw
> <Anti-T> `-+- policy='round-robin 0' prio=1 status=active
> <Anti-T> |- 0:0:3:0 sdb 8:16 active ready running
> <Anti-T> `- 0:0:2:0 sda 8:0 active ready running
> One have 2 tree and one both disk is on the same branch
> One is more secure ?
> Thank you for your help.
> Have a nice day.
The first one has two path groups each with one path and is configured for
failover (no load balancing of I/O). The second has one path group with both
paths in it and I/O will be balanced (round-robin) between them. This is covered
in the man page and other documentation - see the "failover" and "multibus" path
grouping policies.
Regards,
Bryn.
prev parent reply other threads:[~2011-06-14 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 14:46 Multipath conf Christophe BOULLANGER
2011-06-14 14:12 ` Bryn M. Reeves [this message]
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=4DF76C55.4070802@redhat.com \
--to=bmr@redhat.com \
--cc=cbo@info-services.biz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox