[Bug 1032550] Re: [multipath] failed to get sysfs information

Ronald Moesbergen intercommit at gmail.com
Tue Dec 11 15:36:43 UTC 2012


I just retested with the multipath-tools version
'0.4.9-3ubuntu5+lp1032250dbg1', on 2 systems simulatiously. The test
consisted of repeatedly shutting down the fibre port in the switch for
one of the paths. One system survived (see syslog.test2.survived.gz),
one system did not (syslog.test2.broken.gz). The crashdump stuff was
installled and panic_on_oops set to '1', but there were no kernel 'BUG'
or 'OOPS'-en going on this time... The 'failed to get sysfs information'
error is gone, however. It might have been replaced with the following
though:

Dec 11 16:04:44 ealxs00162 udevd[8828]: rename '/dev/disk/by-id/wwn-
0x6006016061e02e008a2d4fa5b307e211.udev-tmp' '/dev/disk/by-id/wwn-
0x6006016061e02e008a2d4fa5b307e211' failed: No such file or directory

Hope this helps.


** Attachment added: "syslog.test2.broken.gz"
   https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3457382/+files/syslog.test2.broken.gz

-- 
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/1032550

Title:
  [multipath]  failed to get sysfs information

Status in “multipath-tools” package in Ubuntu:
  In Progress

Bug description:
  when shutdown switch port of host HBA,  multippath-tool can't get
  correct information  of subpath. by check the "multipath" output,
  some storage device type info disapppear and the failed path always
  stay in path group and don't be clear out.


  mpath2 (3600601601c102900944737e4a73fe011) dm-51 ,
  size=6.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
  |-+- policy='round-robin 0' prio=1 status=active
  | |- #:#:#:#  -    #:#     failed faulty running
  | `- 5:0:2:5  sdcu 70:32   active ready running
  `-+- policy='round-robin 0' prio=0 status=enabled
    |- 5:0:3:5  sdfa 129:192 active ready running
    `- #:#:#:#  -    #:#     failed faulty running
  mpath38 (3600601601c1029008eb6dbe8ae3fe011) dm-59 DGC,VRAID
  size=5.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
  |-+- policy='round-robin 0' prio=1 status=active
  | `- 5:0:2:13 sddf 70:208  active ready running
  `-+- policy='round-robin 0' prio=0 status=enabled
    `- 5:0:3:13 sdfk 130:96  active ready running
  mpath63 (360000970000198700131533030303932) dm-13 EMC,SYMMETRIX
  size=5.6G features='0' hwhandler='0' wp=rw
  `-+- policy='round-robin 0' prio=1 status=active
    |- 5:0:0:8  sdl  8:176   active ready running
    `- 5:0:1:8  sdbd 67:112  active ready running
  mpath95 (360000970000198700131533030323445) dm-43 ,
  size=898M features='0' hwhandler='0' wp=rw
  `-+- policy='round-robin 0' prio=1 status=active
    |- #:#:#:#  -    #:#     failed faulty running
    |- #:#:#:#  -    #:#     failed faulty running
    |- 5:0:0:38 sdas 66:192  active ready running
    `- 5:0:1:38 sdck 69:128  active ready running


  Same time, the syslog show many

  ---------------
  Aug  2 18:25:16 Linux51 multipathd: sdht: failed to get sysfs information
  Aug  2 18:25:16 Linux51 multipathd: sdht: unusable path
  ... ...
  ---------------

  After path  recover, all failed path come back without problem.  there
  is no IP blocked and error happend during fail/recover period.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+subscriptions




More information about the foundations-bugs mailing list