On Thu, 2017-12-07 at 12:49 -0600, Benjamin Marzinski wrote:
> set_no_path_retry() was always updating the queue_if_no_path setting,
> even if it was unnecessary. This caused problems when no_path_retry
> was
> set to a number, where any time __setup_multipath() was called with
> reset, queuing
set_no_path_retry() was always updating the queue_if_no_path setting,
even if it was unnecessary. This caused problems when no_path_retry was
set to a number, where any time __setup_multipath() was called with
reset, queuing automatically restarted, even if there were no usable
paths.
Instead,
