Bug 1731906 - Remove 'aio read size = 4096' setting from default smb.conf
Summary: Remove 'aio read size = 4096' setting from default smb.conf
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
Target Milestone: ---
: RHGS 3.5.z Async Update
Assignee: Anoop C S
QA Contact: Vivek Das
Depends On:
TreeView+ depends on / blocked
Reported: 2019-07-22 11:18 UTC by Anoop C S
Modified: 2020-03-23 13:54 UTC (History)
4 users (show)

Fixed In Version: samba-4.11.6-102.el7rhgs, samba-4.11.6-102.el8rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-03-23 13:53:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:0943 0 None None None 2020-03-23 13:54:15 UTC

Description Anoop C S 2019-07-22 11:18:50 UTC
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):

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).


Comment 8 errata-xmlrpc 2020-03-23 13:53:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.