Chapter 35. Storage

Previously, the mpathpersist utility sometimes overstepped the limit on open files when scanning a large number of devices. As a consequence, mpathpersist terminated unexpectedly.

With this update, mpathpersist now checks the max_fds configuration value and correctly sets the maximum number of open files. As a result, mpathpersist no longer fails when opening too many files. (BZ#1610263)

Previously, in some cases the multipathd daemon was incorrectly calculating the I/O size to use with the readsector0 checker, causing it to do a 0 size read. This could cause the multipathd readsector0 checker to return the wrong result. It is also possible that some SCSI devices do not treat a 0 size read command as valid. With this fix, multipathd now uses the correct size for the readsector0 checker. (BZ#1584228)

Previously, Device Mapper Multipath (DM Multipath) printed an error message after reconfiguring devices for more than 10 seconds. The error was displayed even if the reconfigure was progressing successfully. As a consequence, it sometimes seemed that the reconfigure failed when reconfiguring a large number of devices.

With this update, the timeout limit has been increased from 10 to 60 seconds, and DM Multipath is now much less likely to print incorrect timeout errors when reconfiguring a large number of devices. (BZ#1544958)

Previously, the multipath -l command did not print the sysfs state of paths because the multipath utility did not correctly set path information. With this update, the problem has been fixed, and multipath now prints the sysfs state of paths correctly. (BZ#1526876)

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: