From Ben Marzinski:
There are four changes that are going into RHEL-7.4
1368211: There is a new multipath.conf defaults section parameter, "remove_retries". This sets how may times multipath will retry removing a device that is in-use. Between each attempt, multipath will sleep 1 second. The default is 0, which means that multipath will not retry the remove, which is the current behavior
1169168: There is a new multipath.conf defaults section parameter, "disable_changed_wwids". If this is set to "yes" and the wwid of a path device changes while it is part of a multipath device, multipath will disable access to the path device until the wwid of the path is restored to the wwid of the multipath device. The default is "no", which does not check if a path's wwid has changed, which is the current behavior.
1372032: There is a new multipath.conf devices and defaults section parameter, "detect_path_checker". If set to "yes", multipath will try to detect if the device supports ALUA. If so, the device will automatically use the tur path checker. If not, the path_checker will be selected as usual. Default is "no", which gives the current behavior.
1394059: There is a new multipath.conf parameter for all sections, "max_sectors_kb". This takes a number and sets the max_sectors_kb device sysfs parameter on all path devices and the multipath device to the specified value. If this parameter is not set, multipath does not modify the default max_sectors_kb value for the path devices (which is device dependent), and the multipath device inherits the value from the paths
Section Number and Name:
Describe the issue:
Suggestions for improvement:
The description of the max_sectors_kb parameter has now been added to the 7.4 draft, with the same description that was added to the current 6.9 draft.