Bug 1731906

Summary: Remove 'aio read size = 4096' setting from default smb.conf
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Anoop C S <anoopcs>
Component: sambaAssignee: Anoop C S <anoopcs>
Status: CLOSED ERRATA QA Contact: Vivek Das <vdas>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: gdeschner, puebele, rcyriac, rhs-smb
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Async Update   
Hardware: x86_64   
OS: Linux   
Whiteboard:
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:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-23 13:53:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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

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

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.

https://access.redhat.com/errata/RHSA-2020:0943