All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Brian Bunker <brian@purestorage.com>
Cc: dm-devel@redhat.com
Subject: Re: different LUN numbers under the same dm device
Date: Fri, 08 Jun 2012 08:29:21 +0200	[thread overview]
Message-ID: <4FD19BC1.5020702@suse.de> (raw)
In-Reply-To: <8DCD6D08-35CE-48CC-AC54-7436265C32CB@purestorage.com>

On 06/06/2012 09:27 PM, Brian Bunker wrote:
> Our company produces a multiple port Fibre Channel storage array. We are continually plagued
> by this problem. We get a dm device which combines paths for
different LUN's. We would like
> to understand why this is happening. Wouldn't this problem almost
certainly lead to a data
> corruption?
> 
Most likely; given that the two LUNs indeed refer to different disks.

> Thanks,
> Brian
> 
> 3624a93700a14254d729923840001000b dm-11 PURE,FlashArray
> size=500G features='0' hwhandler='0' wp=rw
> `-+- policy='round-robin 0' prio=1 status=active
>   |- 1:0:0:12 sde  8:64   failed faulty running
>   |- 0:0:0:12 sdd  8:48   failed faulty running
>   |- 0:0:0:10 sdar 66:176 active ready  running
>   `- 1:0:0:10 sdba 67:64  active ready  running
> 
> Of the 4 paths to dm-11, we can see two paths are for LUN 10 and the other two are for LUN 12.
> We have 24 other dm devices which have only the expected 2 paths.
> 
Check the output of 'sg_vpd -p di /dev/sd(e|d|ar|ba)'.

'sde' and 'sdd' should be identical (well, the bits for 'Addressed
logical unit' should be), as should 'sdar' and 'sdab'.
'sde' and 'sdar', on the other hand, should _not_.

Given the above, however, I strongly suspect they are.
Looks like your LUN WWID generation code is buggered.

But I guess you can always blame Nic Bellinger :-)

Greetings to Joern Engel.

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)

      parent reply	other threads:[~2012-06-08  6:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06 19:27 different LUN numbers under the same dm device Brian Bunker
2012-06-06 20:35 ` Mike Snitzer
2012-06-06 20:59   ` Brian Bunker
2012-06-07 22:39     ` Benjamin Marzinski
2012-06-07 23:26       ` Brian Bunker
2012-06-08  6:59         ` Hannes Reinecke
2012-06-08  7:52           ` Mike Christie
2012-06-08 16:35             ` Brian Bunker
2012-06-08 17:05               ` Mike Christie
2012-06-08 17:18                 ` Brian Bunker
2012-06-11  6:38                   ` Hannes Reinecke
2012-06-08  6:37     ` Hannes Reinecke
2012-06-08  6:29 ` Hannes Reinecke [this message]

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=4FD19BC1.5020702@suse.de \
    --to=hare@suse.de \
    --cc=brian@purestorage.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.