From: Hannes Reinecke <hare@suse.de>
To: Alasdair G Kergon <agk@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
christophe varoqui <christophe.varoqui@free.fr>
Subject: [PATCH 0/2] Allow paths for multipath
Date: Mon, 02 Jun 2008 10:52:05 +0200 [thread overview]
Message-ID: <4843B4B5.8070705@suse.de> (raw)
Hi all,
this patchset modifies multipathing to allows zero paths
to a multipath path target.
This is required to make root on multipath working correctly
even when all paths are temporarily down.
Previously multipath would _not_ remove the reference for
the last path from the multipath target. This caused a
reference to a stale/dead device still to be present in
the kernel, which has quite a lot of interesting side effects.
Not the least to multipath itself, which failed to reconnect
the resumed path correctly to the map, causing the same path
to appear twice in the map.
With this patchset we can now shed the last reference, too.
Hence the device can be freed properly from within the kernel
and multipathd is able to setup the correct map once the
paths reappear. And they will even get the same device numbers
again.
Any I/O during that time will be queued if the
'queue_if_no_path' feature is present, otherwise it will
be returned with -EIO. But this is already done correctly
within the dm-mpath module; the only change there is the
lowering of the lowest acceptable path priority group
number, which of course should be '0' now.
Please apply.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
reply other threads:[~2008-06-02 8:52 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=4843B4B5.8070705@suse.de \
--to=hare@suse.de \
--cc=agk@redhat.com \
--cc=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.