All of lore.kernel.org
 help / color / mirror / Atom feed
* multipath and READ_CAPACITY
@ 2014-07-24  8:46 Hannes Reinecke
  2014-07-24  9:00 ` Christophe Varoqui
  0 siblings, 1 reply; 2+ messages in thread
From: Hannes Reinecke @ 2014-07-24  8:46 UTC (permalink / raw)
  To: Christophe Varoqui; +Cc: device-mapper development, Bart Van Assche

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)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: multipath and READ_CAPACITY
  2014-07-24  8:46 multipath and READ_CAPACITY Hannes Reinecke
@ 2014-07-24  9:00 ` Christophe Varoqui
  0 siblings, 0 replies; 2+ messages in thread
From: Christophe Varoqui @ 2014-07-24  9:00 UTC (permalink / raw)
  To: Hannes Reinecke; +Cc: device-mapper development, Bart Van Assche


[-- Attachment #1.1: Type: text/plain, Size: 1433 bytes --]

This sanity check is useful because users can set arbitrary getuid scripts,
and thus corrupt data if their getuid callout is bogus.
Now, this getuid callout facility is a lot less publicized ...
I'd apply the patch, no problem on my side.


On Thu, Jul 24, 2014 at 10:46 AM, Hannes Reinecke <hare@suse.de> wrote:

> 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)
>

[-- Attachment #1.2: Type: text/html, Size: 2009 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-07-24  9:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-24  8:46 multipath and READ_CAPACITY Hannes Reinecke
2014-07-24  9:00 ` Christophe Varoqui

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.