Description of problem: It has been sometime that 'aio read size' parameter has changed its internal implementation/logic to determine whether to perform read in asynchronous mode. With its default being '1' this boils down to the fact that a non-zero value for 'aio read size' would itself is sufficient to enable asynchronous read and is clear from man smb.conf(5). Therefore current setting of 'aio read size' to 4096 is no longer reasonable. From man smb.conf(5): -------------8<----------------8<---------------8<---------------8<------------- aio read size (S) If this integer parameter is set to a non-zero value, Samba will read from files asynchronously when the request size is bigger than this value. Note that it happens only for non-chained and non-chaining reads and when not using write cache. The only reasonable values for this parameter are 0 (no async I/O) and 1 (always do async I/O). -------------8<----------------8<---------------8<---------------8<-------------
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. https://access.redhat.com/errata/RHSA-2020:0943