Re: [dm-devel] no_path_retry configurable per device basis?

[Gianluca Cecchi <gianluca cecchi gmail com>]

Thanks for answering.
why will I still see queue if_if_no_path?
Ok for the kb... it was the same I referred to in my qyestion... ;-)

And what about having a multipath.conf like this?

blacklist {
      devnode "^cciss!c[0-9]d[0-9]*"
}


defaults {
      user_friendly_names yes
      polling_interval 30
      rr_min_io 100
}
      device {
              vendor                  "IBM"
              product                 "1750500"
              getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
              prio_callout            "/sbin/mpath_prio_alua %d"
              hardware_handler        "0"
              path_grouping_policy    group_by_prio
              failback                immediate
              rr_weight               uniform
              path_checker            tur
              no_path_retry 3
      }
multipaths {
      multipath {
              wwid                    3600507630efe0b0c0000000000000600
              alias                   mpath0
              no_path_retry      queue
      }
      multipath {
              wwid                    3600507630efe0b0c0000000000000601
              alias                   mpath1
              no_path_retry      queue
      }
     [snip]
      multipath {
              wwid                    3600507630efe0b0c0000000000000610
              alias                   mpath6
      }
    [snip]
}

what would I see with multipath -l?

As in defaults for this device there is
features 1 queue_if_no_path
and there is no other option configurable per "features" key in device
section....
what would be the effect?
Or in other words, can I disable the "features" key for a device....?
For example setting fir it the no_path_retry that semms applicable to
the device section itself...?


Gianluca