similar to: aio settings for samba 4.3

On Tue, Jul 19, 2016 at 12:42:53PM -0700, Jeremy Allison wrote: > On Tue, Jul 19, 2016 at 12:49:09PM -0500, Russell R Poyner wrote: > > I'm tuning a samba 4.3 install on freebsd and I'm confused about aio > > settings. > > > > I've loaded the freebsd aio kernel module and tried various values > > or aio read size and aio write size, but it seems to

One more data point for comparison I installed the stock samba 4.2 rpm on a centos 7 machine and ran the same diskspd tests against a share configured with: vfs objects = aio_pthread aio read size = 1024 aio read size = 1024 smb2 leases = yes I get 27MB/s with 4k blocks and 145MB/s with 64k blocks. Disabling cacheing by passing the -h switch to diskspd lowered these to 72MB/s

On Thu, Jul 21, 2016 at 12:23:01PM -0500, Russell R Poyner wrote: > One more data point for comparison > > I installed the stock samba 4.2 rpm on a centos 7 machine and ran > the same diskspd tests against a share configured with: > vfs objects = aio_pthread > aio read size = 1024 > aio read size = 1024 > > smb2 leases = yes > > I get 27MB/s with 4k

Am 21.07.2016 um 20:56 schrieb Russell R Poyner: > Jeremy, > > I think this is exactly a complex interaction between FreeBSD and > Samba. Best guess would be some system call that is fast in linux but > slow in FreeBSD holding things back. > > Russ > > On 07/21/2016 01:00 PM, Jeremy Allison wrote: >> On Thu, Jul 21, 2016 at 12:23:01PM -0500, Russell R Poyner

When you say “real symlinks on OSX” do you mean an “alias” that Finder would create? Or a Unix-type symlink using the “ ln -s file link” command in Terminal? A Finder alias is not the same as a Unix-type symlink. My NAS runs Debian Linux with version 4.3.11 of smbd; my clients are all OSX Mojave. If I create an alias using Finder on the NAS, it behaves like a normal alias in OSX UNLESS I move

On Thu, Jul 21, 2016 at 10:50:16PM +0200, Achim Gottinger wrote: > > > Am 21.07.2016 um 20:56 schrieb Russell R Poyner: > >Jeremy, > > > >I think this is exactly a complex interaction between FreeBSD and > >Samba. Best guess would be some system call that is fast in linux > >but slow in FreeBSD holding things back. > > > >Russ > > >

Jeremy, I think this is exactly a complex interaction between FreeBSD and Samba. Best guess would be some system call that is fast in linux but slow in FreeBSD holding things back. Russ On 07/21/2016 01:00 PM, Jeremy Allison wrote: > On Thu, Jul 21, 2016 at 12:23:01PM -0500, Russell R Poyner wrote: >> One more data point for comparison >> >> I installed the stock samba

I'm struggling with a permission problem on a samba server that is configured to resolve unix uids and gids via nss using sssd. This mostly works. The windows side sees files as being owned by SID=S-1-22-<unix uid of user> and the group is SID=S-1-22-<unix gid of group> This all works fine for files owned by the windows user, or files that are world readable, but fails for

I'm looking into trying out AIO on one of our file servers in the office but I can't find any info on what the values for "aio read size" and "aio write size" correspond to. Is it a buffer size of some sort or a tuning type parameter were it allows the socket to read/write x blocks? Thanks, David Miller

I have 20+ freebsd 10 samba 4 servers joined to our local microsoft active directory. At the moment things work well enough. However the windows administrator wants to tighten his AD security by requiring tls encrypted ldap. When I add: ldap ssl = start_tls ldap ssl ads = yes cldap port = 389 the net ads commands fail: net ads testjoin Failed to issue the StartTLS instruction: Connect error

Maybe it''s something I''m doing wrong, but I have a 15gb image that I use with disk = [ "tap:aio:/root/images/vista32.img,hda,w" ] It was working fine on Friday, but today it failed to boot with an error message. The same works fine when I replace "tap:aio:" with "file:". It seems like qemu-dm tries to open the file with the "aio:" still

hi, i just have some questions about specific (uncommon) compile options and aio-settings in smb.conf: Asynchronous IO Support ======================= "Experimental support for async IO has been added to smbd for certain platforms. To enable this new feature, Samba must be compiled to include the --with-aio-support configure option. In addition, the "aio read size" and

I have never been able to get tap:aio devices running. When I try it in a Linux PV domain, it says: XENBUS: Waiting for devices to initialise: 295s... And they don''t work in my GPLPV drivers, which is the problem I am trying to solve, but I''d like to see them work under Linux first. Is there anything extra I need to do? I have loaded the xenblktap module (forgot to do this

hi, i'm trying to get the asynchronous file transfer to work on a FC4 for the latest samba verion (3.0.20b). The things i've done: ./configure --with-aio-support ... included "aio read size = 1" and "aio write size = 1" in the smb.conf file What did i forget?? michiel ========================= uname -a Linux wired11 2.6.12-1.1398_FC4 #1 Fri Jul 15 00:52:32 EDT

Hello list, I setup Iometer to test AIO for 100% random read. If "Transfer Request Size" is more than or equal to 256 kilobytes,in the beginning the transmission is good. But 3~5 seconds later,the throughput will drop to zero. Server OS: Ubuntu Server 14.04.1 LTS Samba: Version 4.1.6-Ubuntu Dialect: SMB 2.0 AIO settings : aio read size = 1 aio write size = 1 vfs objects =

Looked through the smb.conf.5 from 3.0.20pre2 for additional info on the aio settings but didn't seem to find them. I'm setting this up on AIX 5.2 and just wondered what where recommended starting values...and non-zero values activate the AIO code paths? Cheers, Bill

I'm trying to install samba-3.0.20 on aix 5.2, and I don't want to use aio, but the build process is compiling it in anyway. By default, it isn't supposed to build in aio support, but it does. When I pass --with-aio-support=no to configure, it also builds in support. It builds in aio support whether I use gcc or xlc. Here's what ldd shows: # ldd bin/smbd bin/smbd needs:

when installing samba from FreeBSD ports collection, I can choose AIO support, which leads to ... checking whether to support asynchronous io... yes checking for aio_read in -lrt... no checking for asynchronous io support... no checking for 64-bit asynchronous io support... no does it mean aio was not enabled ? Cheers, Ilia Chipitsine

Hi list, I have been trying to enable AIO on ARMv5 Samba built with kernel headers 2.6.31.8, the configure indicated that AIO is supported via kernel headers and all went smooth (regarding the build process). Once I added the smb.conf 'aio write size=1' and tried to perform a file copy to the Samba share I noticed that 32K of the file (of the 1GB file) have been copied to the share but

Hi, xen-3.0.3-41.el5 on RHEL5.1 I''m trying to use tap:aio thusly: disk = [ ''file:/var/lib/xen/images/webmail.golden.net.img,hda,w'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users