From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: [BUG REPORT] multipath-tools: -EIO even if no_path_retry is set
Date: Tue, 23 Jun 2009 11:55:44 +0900 [thread overview]
Message-ID: <4A404430.4050103@ct.jp.nec.com> (raw)
Hi,
I found a bug below in multipath-tools.
I don't have a patch but just report it for now.
Problem
-------
Application receives -EIO even if 'no_path_retry = queue' is set,
when all paths are down and deleted nearly simultaneously.
Why does it happen?
-------------------
When 'no_path_retry = queue' is set in multipath.conf,
multipathd will do the following on table (re)load:
1. load the table *without* 'queue_if_no_path'
2. resume the table
3. send a message to the dm device to set 'queue_if_no_path'
So there is a small window inbetween the step 2 and step 3 where
failed I/O is not queued.
How should it be fixed?
-----------------------
If 'no_path_retry' is set, multipathd puts 'queue_if_no_path'
in 'features' field of the table which is loaded.
Workaround
----------
Use 'features = "1 queue_if_no_path"' together with 'no_path_retry'
in multipath.conf.
Thanks,
Kiyoshi Ueda
reply other threads:[~2009-06-23 2:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A404430.4050103@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox