*multipathd* can now correctly set APTPL when registering keys on path devices
Previously, the *multipathd* service did not track which devices registered their persistent reservation keys with the Activate Persist Through Power Loss (APTPL) option. As a consequence, registrations always lost the APTPL setting.
With this update, the problem has been fixed:
* If you set the "reservation_key" option to a file in the `multipath.conf` configuration file, *multipathd* now keeps the APTPL setting automatically.
* If you set "reservation_key" to a specific key, you can now add the ":aptpl" string at the end of the key in "reservation_key", which enables APTPL for it. Set this to match the APTPL setting used when registering the key.
Because there is no Nimble Storage in our lab, could you help provide test result once the package is available?
Multipath now supports an optional extension to the reservation_key parameter. You can now set reservation_key to "<key>:aptpl". This will inform multipathd to set the APTPL bit when registering keys on paths, when they come back up. For this to work correctly, you must also set --param-aptpl when using mpathpersist to register the key. If you set reservation_key to "file", multipath will automatically track which devices need the APTPL bit set by multipathd, depending on which devices you register keys with using the --param-aptpl option
Could you test if the new option works well on Nimble Storage?
Thanks in advance!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.