RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

upstream has a patch for 3.5 that can potentially increase performances on ext4/xfs by using posix_fallocate.

We should consider applying it to RHEL6 samba.
Potentially we could also consider turning strict allocate to true by patching it in as a default in loadparm.c

The upstream bug is here: https://bugzilla.samba.org/show_bug.cgi?id=7835

+1 from me. Keep me posted on the progress on this one. It can *double* Samba
performance in applications which write large files. I will push to get "strict
allocate" set to "true" in upstream code in 3.6.0, but Red Hat can gain this
performance now if you apply this change to your 3.5.x tree.

Jeremy.

Jeremy tested with:

"In tests done on an ext4 file system, changing to "strict allocate =
yes" and using the posix_fallocate() call in this way increased the
write performance of Samba by 2/3 on a NETGEAR ReadyNAS box as
tested by the Intel NASPT test tool, available here:

http://software.intel.com/en-us/articles/intel-nas-performance-toolkit/

The specific tests used to measure the performance increase were the
"File Copy to NAS" and the "HD Video Record" tests."

We should do the same or similar for all the filesystems we support with Samba - at least ext3, ext4, xfs.

Thanks,
-Eric

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0582.html