Comment 17 for bug 1435706

To me fix doesn't actually appear to work. After upgrading to multipath-tools 0.4.9-3ubuntu7.4on an amd64 trusty and rebooting, the fast_io_fail_tmo and dev_loss_tmo values do not get written to sysfs:

$ grep . /sys/class/fc_remote_ports/*/*_tmo
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-3:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-3:0-1/fast_io_fail_tmo:off

The device stanza from multipath.conf contains the following:

 device {
  vendor "DGC|EMC"
  product "RAID [0-9]*|VRAID|SYMMETRIX.*"
  path_grouping_policy group_by_prio
  getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
  path_selector "round-robin 0"
  path_checker emc_clariion
  features "0"
  hardware_handler "1 emc"
  prio emc
  failback immediate
  rr_weight uniform
  no_path_retry queue
  rr_min_io 100
  fast_io_fail_tmo 3
  dev_loss_tmo 2147483647
 }

FWIW, I can manually set the sysfs settings to the desired values:

$ echo 3 | sudo tee /sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo
3
$ echo 2147483647 | sudo tee /sys/class/fc_remote_ports/rport-*/dev_loss_tmo
2147483647
$ grep . /sys/class/fc_remote_ports/*/*_tmo
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-3:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-3:0-1/fast_io_fail_tmo:3

Tore