The `multipathd readsector0` checker now returns the correct result
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.
Multipathd will now request the correct number of blocks for the readsector0 checker in all cases. I don't know if that's the root cause of this issue, but it should make the checker issue the correct command. If the controller is still not honoring it, it is more likely a controller issue.
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.