From: David Jeffery <djeffery@redhat.com>
To: dm-devel@redhat.com
Subject: [PATCH] multipath queues build invalid requests when all paths are lost
Date: Fri, 31 Aug 2012 11:04:28 -0400 [thread overview]
Message-ID: <20120831150428.GA31566@fury.redhat.com> (raw)
The DM module recalculates queue limits based only on devices which currently
exist in the table. This creates a problem in the event all devices are
temporarily removed such as all fibre channel paths being lost in multipath.
DM will reset the limits to the maximum permissible, which can then assemble
requests which exceed the limits of the paths when the paths are restored. The
request will fail the blk_rq_check_limits() test when sent to a path with
lower limits, and will be retried without end by multipath.
This becomes a much bigger issue after fe86cdcef73ba19a2246a124f0ddbd19b14fb549.
Previously, most storage had max_sector limits which exceeded the default
value used. This meant most setups wouldn't trigger this issue as the default
values used when there were no paths were still less than the limits of the
underlying devices. Now that the default stacking values are no longer
constrained, any hardware setup can potentially hit this issue.
This proposed patch alters the DM limit behavior. With the patch, DM queue
limits only go one way: more restrictive. As paths are removed, the queue's
limits will maintain their current settings. As paths are added, the queue's
limits may become more restrictive.
Signed-off-by: David Jeffery <djeffery@redhat.com>
---
dm-table.c | 2 --
dm.c | 2 ++
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index f900690..5e7e3ca 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -1222,8 +1222,6 @@ int dm_calculate_queue_limits(struct dm_table *table,
struct queue_limits ti_limits;
unsigned i = 0;
- blk_set_stacking_limits(limits);
-
while (i < dm_table_get_num_targets(table)) {
blk_set_stacking_limits(&ti_limits);
diff --git a/drivers/md/dm.c b/drivers/md/dm.c
index 4e09b6f..fbf89d5 100644
--- a/drivers/md/dm.c
+++ b/drivers/md/dm.c
@@ -1832,6 +1832,7 @@ static void dm_init_md_queue(struct mapped_device *md)
blk_queue_make_request(md->queue, dm_request);
blk_queue_bounce_limit(md->queue, BLK_BOUNCE_ANY);
blk_queue_merge_bvec(md->queue, dm_merge_bvec);
+ blk_set_stacking_limits(&md->queue->limits);
}
/*
@@ -2419,6 +2420,7 @@ struct dm_table *dm_swap_table(struct mapped_device *md, struct dm_table *table)
if (!dm_suspended_md(md))
goto out;
+ limits = md->queue->limits;
r = dm_calculate_queue_limits(table, &limits);
if (r) {
map = ERR_PTR(r);
next reply other threads:[~2012-08-31 15:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 15:04 David Jeffery [this message]
2012-09-04 14:58 ` multipath queues build invalid requests when all paths are lost Mike Snitzer
2012-09-04 16:10 ` Mike Snitzer
2012-09-04 16:12 ` Mike Snitzer
2012-09-08 16:50 ` Mikulas Patocka
2012-09-12 15:37 ` [PATCH] dm mpath: only retry ioctl if queue_if_no_path was configured Mike Snitzer
2012-09-12 17:01 ` Mikulas Patocka
2012-09-12 19:37 ` [PATCH] dm table: do not allow queue limits that will exceed hardware limits Mike Snitzer
2012-09-14 20:41 ` [PATCH v2] " Mike Snitzer
2012-09-17 19:44 ` David Jeffery
2012-09-17 19:52 ` Alasdair G Kergon
2012-09-18 11:40 ` Alasdair G Kergon
2012-09-18 13:02 ` Mike Snitzer
2012-09-21 15:37 ` [PATCH v3] dm: re-use live table's limits if next table has no data devices Mike Snitzer
2012-09-17 20:24 ` [PATCH v2] dm table: do not allow queue limits that will exceed hardware limits Alasdair G Kergon
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=20120831150428.GA31566@fury.redhat.com \
--to=djeffery@redhat.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;
as well as URLs for NNTP newsgroup(s).