From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Setting up a multipath device
Date: Mon, 08 May 2006 23:33:15 +0200 [thread overview]
Message-ID: <1147123995.27764.46.camel@localhost.localdomain> (raw)
In-Reply-To: <445DFD9D.4040402@voltaire.com>
Le dimanche 07 mai 2006 à 17:01 +0300, Erez Zilber a écrit :
> Some more questions:
>
> 1. I couldn't find the config file. Where is it located? Is there any
> documentation about it?
The config file normal location is /etc/multipath.conf
> 2. How can I configure fancy naming for devices (instaed of using
> something like /dev/mapper/3600c0ff00000000007c1d121c397f503) in
> the config file?
Have a look at the templates provided with the upstream package.
> 3. How can I config the delay from the time that a device has failed
> until the dm moves to the next active device? Again, I understand
> that I should use the config file somehow.
>
Ditto.
> I tried to run the following test: I created a multipath device with 2
> physical devices (/dev/sda & /dev/sdb). I started running traffic on the
> multipath device. All traffic ran through /dev/sda. Then, I disconnected
> the iSCSI target that was represented by /dev/sda. After some time, the
> traffic was directed to /dev/sdb. I stopped the traffic, disconnected
> the iSCSI target that was represented by /dev/sdb and reconnected
> /dev/sda. Now, if I run `multipath -l`, I see the following output:
>
> 3600c0ff00000000007c1d121c397f503
> [size=10 GB][features=0][hwhandler=0]
> \_ round-robin 0 [prio=0][enabled]
> \_ 0:0:0:0 sda 8:0 [failed][undef]
> \_ round-robin 0 [prio=0][enabled]
> \_ 1:0:0:0 sdb 8:16 [failed][faulty]
>
> /dev/sdb is dead and I'm ok with it. However, /dev/sda is alive. I was
> able to run the following command:
>
> dd if=/dev/sda of=/dev/null count=100000
>
> However, if I run the following command:
>
> dd if=/dev/mapper/3600c0ff00000000007c1d121c397f503 of=/dev/null
> count=100000
>
> This is what I get:
>
> dd: reading `/dev/mapper/3600c0ff00000000007c1d121c397f503':
> Input/output error
> 0+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 0.00067 seconds, 0.0 kB/s
>
> Can't it recongnize that a device that has failed (/dev/sda) is back to
> life?
>
Is the daemon (multipathd) running ? The daemon takes care of path
revalidation.
Regards,
cvaroqui
prev parent reply other threads:[~2006-05-08 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 14:08 Setting up a multipath device Erez Zilber
2006-05-04 14:49 ` Christophe Varoqui
2006-05-04 15:28 ` Erez Zilber
2006-05-04 18:55 ` Christophe Varoqui
2006-05-07 14:01 ` Erez Zilber
2006-05-08 21:33 ` Christophe Varoqui [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=1147123995.27764.46.camel@localhost.localdomain \
--to=christophe.varoqui@free.fr \
--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.