[Bug 1815599] Re: multipath shows '#:#:#:#' for iscsi device after error injection

[Frank Heimes]

Some configurations are possible to face this and similar issues, please have a look here:
http://public.dhe.ibm.com/software/dw/linux390/lvc/zFCP_Best_Practices-BB-Webcast_201805.pdf

** Also affects: ubuntu-z-systems
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1815599

Title:
  multipath shows '#:#:#:#' for iscsi device after error injection

Status in Ubuntu on IBM z Systems:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  Problem Description:
  After error injection(reset one node for storage), 1 of 4 luns show '####' for half paths

  ---uname output---
  root at ilzlnx4:~# uname -a
  Linux ilzlnx4 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:43:05 UTC 2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  
  --iscsi initiator
  root at ilzlnx4:~# dpkg  -l  | grep iscsi
  ii  open-iscsi                            2.0.874-5ubuntu2.6                s390x        iSCSI initiator tools

   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1 Mapping 4 luns via open-iscsi from SVC
  2 Running IO on these luns
  3 Run storage side error inject 'node reset' for SVC (about start at ?2019/02/11 05:14?)
  4 half of one luns' path show '#:#:#:#' and never recovered without manual intervention


  [2019/02/11 05:53:13]  INFO send: multipath -ll | cat  
  [2019/02/11 05:53:29]  INFO  
  3600507638085814a980000000000000a dm-3 IBM,2145 
  size=10G features='3 queue_if_no_path queue_mode mq' hwhandler='0' wp=rw 
  |-+- policy='service-time 0' prio=50 status=active 
  | |- 4:0:0:3 sdr 65:16 active ready running 
  | `- 6:0:0:3 sdu 65:64 active ready running 
  `-+- policy='service-time 0' prio=10 status=enabled 
    |- 1:0:0:3 sdh 8:112 active ready running 
    `- 2:0:0:3 sdl 8:176 active ready running 
  3600507638085814a9800000000000009 dm-4 IBM,2145 
  size=10G features='3 queue_if_no_path queue_mode mq' hwhandler='0' wp=rw 
  |-+- policy='service-time 0' prio=50 status=active 
  | |- 1:0:0:1 sdf 8:80  active ready running 
  | `- 2:0:0:1 sdj 8:144 active ready running 
  `-+- policy='service-time 0' prio=0 status=enabled 
    |- #:#:#:# sdo 8:224 active faulty running 
    `- #:#:#:# sds 65:32 active faulty running 
  3600507638085814a9800000000000008 dm-2 IBM,2145 
  size=10G features='3 queue_if_no_path queue_mode mq' hwhandler='0' wp=rw 
  |-+- policy='service-time 0' prio=50 status=active 
  | |- 4:0:0:2 sdq 65:0  active ready running 
  | `- 6:0:0:2 sdt 65:48 active ready running 
  `-+- policy='service-time 0' prio=10 status=enabled 
    |- 2:0:0:2 sdk 8:160 active ready running 
    `- 1:0:0:2 sdg 8:96  active ready running 
  3600507638085814a9800000000000006 dm-5 IBM,2145 
  size=10G features='3 queue_if_no_path queue_mode mq' hwhandler='0' wp=rw 
  |-+- policy='service-time 0' prio=50 status=active 
  | |- 4:0:0:0 sdm 8:192 active ready running 
  | `- 6:0:0:0 sdp 8:240 active ready running 
  `-+- policy='service-time 0' prio=10 status=enabled 
    |- 1:0:0:0 sde 8:64  active ready running 
    `- 2:0:0:0 sdi 8:128 active ready running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1815599/+subscriptions