All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Bart Van Assche <bvanassche@acm.org>
Subject: multipath and READ_CAPACITY
Date: Thu, 24 Jul 2014 10:46:31 +0200	[thread overview]
Message-ID: <53D0C7E7.6090806@suse.de> (raw)

Hi Christophe,

I've had a customer issue where someone complained that multipath 
would reject paths if they are in ALUA 'standby'.
As it turns out, SPC-3 does _not_ require the READ_CAPACITY command 
to be implemented if a target port is in standby.
Consecutively, linux would register this path with a capacity of 
'0', and multipath would reject the path in ev_add_path().

Which makes we wonder, do we actually _need_ the check for a matched 
capacity?
With VPD page 0x83 pretty much standard as of now (and I'm reasonbly 
sure we'll reject any device _not_ providing VPD page 0x83 anyway) 
we basically have to rely on that information.
IE if the WWID is identical we have assume the devices are 
identical. So it would make sense to just remove the check altogether.

Thoughts?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

             reply	other threads:[~2014-07-24  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  8:46 Hannes Reinecke [this message]
2014-07-24  9:00 ` multipath and READ_CAPACITY Christophe Varoqui

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=53D0C7E7.6090806@suse.de \
    --to=hare@suse.de \
    --cc=bvanassche@acm.org \
    --cc=christophe.varoqui@opensvc.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 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.