similar to: aio-pthread, conflicting param info

Meanwhile it appears to contradict. Is there any reason not to update the vfs doc to reflect the old situation pre-bugfix and the current suggested values? On 8 March 2018 9:28:30 pm Jeremy Allison <jra at samba.org> wrote: > On Thu, Mar 08, 2018 at 09:00:48PM +0000, Stilez via samba wrote: >> In the vfs pages for aio_pthread, it gives as an example for aio read/write >>

On Thu, Mar 08, 2018 at 09:00:48PM +0000, Stilez via samba wrote: > In the vfs pages for aio_pthread, it gives as an example for aio read/write > size, 1024 for each and states an "appropriate" value must be set. > > Byt in smb.conf it states that the only reasonable values are 0 or 1 (also > that there's a default = 1 so no value need be given explicitly). > >

On a related note: Some time ago, you instructed a user to use the following aio_pthread parameter:     aio_pthread:aio open = true This is not undocumented in the man page. Does the parameter have any effect, and what is the effect? Although I tried for a while, I couldn't locate your original message. I don't remember whether it was posted on bugzilla or on a mailing list, but I

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

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

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

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 make no difference in the speed. Using MS diskspd against a samba share from a fast zfs pool I get something like 25MB/s tops. That's well below the capacity of my Gb network and

Thank you. So, If I understand correctly, "ordinary" "wide links = yes", means Samba *will* traverse an existing symlink that points outside the root of the share, if permissions allow. However because it *also* disables SMB1 Unix extensions, it *also* prevents the user from creating or modifying symlinks on the share, so in wffect it inherently prevents this being

I'd like to understand reasonably fully,, the difference between the two options "wide links" and "allow insecure wide links" in smb.conf. The docs make them sound very similar but as there are obvious security implications for anything to do with symlink scope, it's important to know what each of them allows/blocks and where they differ. Interestingly, only the

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 =

As mentioned in another thread, I notice that the params used to control symlinks feel a bit inefficient and inelegant, and quite limited. I think there might be a good opportunity to simplify and also make their management in Samba more powerful and adaptable to use-cases. I'm guessing this list is a good enough starting point to propose a smb.conf param change to this area and see what

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

Thanks - that much I (pretty much) got. Its really the "wide links" option that isn't well distinguished/clarified. *insecure* wide links is much more clear, although the detail you've given helps a lot. What exactly is the "ordinary" "wide links = yes" option going to do (with or without Unix extensions), and how does it compare/how much exposure to

i try to change one of my images from lvm to file with dd if=/dev/vps/centos of=/root/mj.img the fiel whas created byt will not ok i bigin boot but failed i remember the system can''t find the lvm groups i not remember anymore _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi list, I have this problem of (relatively) poor samba read performance. Read performance is constantly, reproducibly lower than write performance and I can't really understand why. Here is the server configuration : dual octocore Opteron 6128, 32 GB RAM Adaptec 6445 RAID card 36x 2TB Hitachi SATA drives (raid 60) Sustained local disk throughput: over 850 MB/s write, over 1.4 GB/s read.

I'm trying to learn more about samba by experimenting with samba on FreeNAS. This involves a certain amount of reading how default smb4.conf parameters are set in FreeNAS and then reading the manpages for those parameters. Async I/O is implemented in samba in freenas via the aio_pthread VFS module. The manpage for vfs_aio_pthread states: "the smb.conf parameters aio read size and aio

Hello list, I am looking to enable samba aio on my Wheezy test box (I have version 4.1.17 from back ports). The output of smbd -b shows that the stable packages for my distro are not compiled using --with-aio-support. It appears that without recompiling I can use vfs objects = aio_pthread to achieve a similar effect? I'm aware that this somewhat dips into Debian specifics, but I figured

On Thu, Mar 01, 2018 at 10:48:02AM +0000, Stilez Stilezy wrote: > As mentioned in another thread, I notice that the params used to control > symlinks feel a bit inefficient and inelegant, and quite limited.  I think > there might be a good opportunity to simplify and also make their management in > Samba more powerful and adaptable to use-cases.  I'm guessing this list is a >

Hi all, I am using samba 4.10.7 and it seems to have bug for using @group in valid or invalid conf (?). And i can't find fixed patch in later release. I describe this issue detail below: 1. Firstly, there is my samba conf below (Add @d_group in "invalid users"): (smb_share.conf) [f1] path = /home/f1 write list = "admin" "@Administrator_Group"

Hi forks: I've been testing SMB2 with samba 3.6.4 performance these days, and I find a weird benchmark that SMB2 write performance is slower than SMB1 in 10Gb ethernet network. Server ----------------------- Linux: Redhat Enterprise 6.1 x64 Kernel: 2.6.31 x86_64 Samba: 3.6.4 (almost using the default configuration) Network: Chelsio T4 T420-SO-CR 10GbE network adapter RAID: Adaptec 51645 RAID