All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Nikanth Karthikesan <knikanth@suse.de>
Subject: Re: [PATCH] Allow zero paths for multipath priority groups
Date: Tue, 21 Jul 2009 16:46:59 +0200	[thread overview]
Message-ID: <4A65D4E3.9050405@suse.de> (raw)
In-Reply-To: <20090720203753.GG32330@agk-dp.fab.redhat.com>

Alasdair G Kergon wrote:
> On Wed, Jul 08, 2009 at 02:15:39PM +0530, Nikanth Karthikesan wrote:
>> From: Hannes Reinecke <hare@suse.de>
>> Subject: Allow zero paths for multipath priority groups
>>
>> For correct handling of the all-paths-down scenario we have to
>> allow zero paths as a valid argument for priority groups.
>  
> That seems counter-intuitive.
> Can you be more specific, with example scenarios?
> 
Currently we're not allowing the last path to be removed
from a multipath target. With earlier kernel revisions
this wasn't a problem as dev_loss_tmo didn't work correctly
and so in effect no devices were ever removed from the system.

However, with newer kernels dev_loss_tmo works correctly, so
any dead path will be removed from the system.
So when the last path goes down, we're having a stale reference
to an sdev which for all intents and purposes should have been
removed.

And even worse, when this path comes back the SCSI subsystem
isn't even able to assign it to the old device number, as this
is already taken.

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:[~2009-07-21 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  8:45 [PATCH] Allow zero paths for multipath priority groups Nikanth Karthikesan
2009-07-20 20:37 ` Alasdair G Kergon
2009-07-21 14:46   ` Hannes Reinecke [this message]
2009-07-21 14:55     ` Alasdair G Kergon
2009-07-22  6:08       ` Hannes Reinecke

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=4A65D4E3.9050405@suse.de \
    --to=hare@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=knikanth@suse.de \
    /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.