search for: wsize

..., I note that the "Howto Automount GlusterFS" page at http://www.gluster.org/community/documentation/index.php/Howto_Automount_GlusterFS has been deleted. Is automounting no longer supported? His auto.master file is as follows (sorry for the wrapping): w1 -rw,intr,bg,v3,rsize=16384,wsize=16384,retrans=10,timeo=20,hard,lock,defaults,noatime,async 10.1.50.2:/& w2 -rw,intr,bg,v3,rsize=16384,wsize=16384,retrans=10,timeo=20,hard,lock,defaults,noatime,async 10.1.50.3:/& mathbio -rw,intr,bg,v3,rsize=16384,wsize=16384,retrans=10,timeo=20,hard,lock,defaults,noatime,async...

hi, guys: Today when i typed "mount " command on the server and found this message: .. ... 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp/share type nfs ( rw, bg, soft,rsize=8192,wsize=8192,addr=192.168.9.252) 192.168.9.252: /home/share/tmp on /net/tmp...

...more like that: --- nfsmount/main.c~ 2004-02-12 03:19:14.000000000 +0100 +++ nfsmount/main.c 2004-05-27 13:31:19.000000000 +0200 @@ -20,9 +20,9 @@ static char *progname; static struct nfs_mount_data mount_data = { .version = NFS_MOUNT_VERSION, - .flags = NFS_MOUNT_NONLM, - .rsize = 1024, - .wsize = 1024, + .flags = NFS_MOUNT_NONLM | NFS_MOUNT_VER3 | NFS_MOUNT_TCP, + .rsize = 8192, + .wsize = 8192, .timeo = 7, .retrans = 3, .acregmin = 3, -- USB is for mice, FireWire is for men! sUse lINUX ag, n?RNBERG

...booted workstation and create another file; this time, it is created as root: -rw-r--r-- 1 root root 0 Feb 26 16:31 bar 3. I checked the /proc/mounts and notice there are differences in the NFS options it has accepted during mount: rootfs / rootfs rw 0 0 /dev/root / nfs rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=null,addr=192.16.10.5 0 0 192.16.10.5:/tftpboot /mnt/test nfs rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.16.5 0 0 4. I try to append NFS options to my APPEND line to force: NFS version3, change r/ws...

I have this NFS client that used to be on Red Hat 7.3. For mounting user home directories I used this line in /etc/auto.master file: /home yp:auto.home rw,rsize=8192,wsize=8192 Moved the box to CentOS 4... The format of the file changed, so I attempted something like this: /home -rw,rsize=8192,wsize=8192 yp:auto.home No habla. Doesn't work. The rsize and wsize options seems to be ignored (I type "mount", and they are not there). Yup, I reloaded c...

...2.4.24) work correctly. Smbclient work correctly with new kernels. Report error from /var/log/messages for kernel 2.6.11.11 and 2.6.11.12: Jun 15 09:29:03 darkknight kernel: smb_add_request: request [c5595e80, mid=29] timed out! Jun 15 09:29:03 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-5 Jun 15 09:33:48 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-512 Jun 15 09:41:05 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-512 Jun 15 09:48:05 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_r...

Hello. We have a number of Xen 3.4.2. boxes which have constant iowaits at around 10% with spikes up to 100% when accessing data over NFS. We have been unable to nail down the issue. Any advice? System info: release : 2.6.18-194.3.1.el5xen version : #1 SMP Thu May 13 13:49:53 EDT 2010 machine : x86_64 nr_cpus : 16 nr_nodes

...>> >> #### this is a part from /proc/self/mountinfo ######## >> 33 20 0:23 / /home/builds ro,relatime - cifs //10.30.20.61/builds >> ro,sec=ntlm,unc=\\10.30.20.61\builds,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.30.20.61,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 >> 32 20 0:24 / /home/platform ro,relatime - cifs //10.30.20.61/platform >> ro,sec=ntlm,unc=\\10.30.20.61\platform,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.30.20.61,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 >> >> and after t...

In case anyone's interested, I followed up in the linux-nfs mailing list: https://marc.info/?l=linux-nfs&m=156887818618861&w=2 Thanks, Alkis On 9/15/19 10:51 AM, Alkis Georgopoulos wrote: > I think I got it. > > Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. > By lowering this to 32K, all issues are gone, even with the default > timeo=7. And nfsroot=xxx client responsiveness is a whole lot better. > > I think when nfsmount was initially written, the default rsize/wsize > were much lower, which matched the timeo=7. > > N...

...smbfs guest,ro 0 0 #### this is a part from /proc/self/mountinfo ######## 33 20 0:23 / /home/builds ro,relatime - cifs //10.30.20.61/builds ro,sec=ntlm,unc=\\10.30.20.61\builds,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.30.20.61,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 32 20 0:24 / /home/platform ro,relatime - cifs //10.30.20.61/platform ro,sec=ntlm,unc=\\10.30.20.61\platform,username=,uid=0,noforceuid,gid=0,noforcegid,addr=10.30.20.61,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 and after this entrys, there are my mounting...

...killed it after 15 minutes. I was going to try compiling Linux kernels on the various domU''s to test for stability, but that''s excruciatingly slow too. Following the instructions here: http://nfs.sourceforge.net/nfs-howto/performance.html I''ve been playing with rsize, wsize and sync mount options. As far as I can see, any rsize/wsize other than the default is slower than the default choice (I couldn''t find out what it is, but it _seems_ to be 1K/1K). The ''sync'' mount option has further catastrophic effects on write performance. I also not...

...ice for writing to - */ +/* Open the audio device for writing. */ int ao_plugin_open(ao_device *device, ao_sample_format *format) { ao_irix_internal *internal = (ao_irix_internal *) device->internal; - ALpv params[2]; + ALpv params; int dev = AL_DEFAULT_OUTPUT; int wsize = AL_SAMPLE_16; - - internal->nChannels = channels; - - if (alSetQueueSize(internal->alconfig, BUFFER_SIZE) < 0) { - fprintf(stderr, "alSetQueueSize failed: %s\n", - alGetErrorString(oserror())); + if (alSetQueueSize(internal->alconfig, AO_IRIX_BUFFER_SIZE) < 0) { + f...

Hi, When I do the "make install-tools" with xen-4.2-unstable, there are some errors about "warn_unused_result". Is it the error in code or the error in the compiling environment? Thank you so much. gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .tapdisk-queue.o.d

...sily with cifs: >//vienas01.andritz.com/HIPASE on /media/HIPASE_Q type cifs >(rw,nosuid,nodev,relatime,vers=1.0,cache=strict,username=<snip>,domain=<sni >p>,uid=1000,forceuid,gid=1000,forcegid,addr=172.24.180.161,file_mode=0755, >dir_mode=0755,nounix,mapposix,rsize=61440,wsize=65536,echo_interval=60,a >ctimeo=1,user=<snip>) > >The problem seems to have appeared with 2:4.2.14+dfsg-0+deb8u7: >http://metadata.ftp- >master.debian.org/changelogs/main/s/samba/samba_4.2.14+dfsg- >0+deb8u7_changelog > >A very old smbclient (Ubuntu 12.04) was...

...er at testdm12:~$ mount ................. //devstation.samdom.example.com/data on /mnt/test type cifs (rw,relatime,vers=3.1.1,sec=krb5,cruid=0,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.141,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,noperm,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1) //devstation.samdom.example.com/Mtest1 on /mnt/testmount1 type cifs (rw,relatime,vers=3.1.1,sec=krb5,cruid=0,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.141,file_mode=0755,dir_mode=0755,soft,nounix,serverino,...

...nel-4.9.0-13 - problem exists In debian10 - kernel-4.19.0-12 - problem exist In debian8 - kernel 3.16.0-11-amd64 - problem not exists In debian9 - kernel 3.16.0-11-amd64 - problem not exists storage mount from storage NetApp storage:/vmail on /vmail type nfs (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.19.19.19,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=10.19.19.19) cat /etc/fstab storage:/vmail??? /vmail??? nfs??? rw,sec=sys,noexec,noat...

...t /documents as /mnt/documents and all data is present. However, if I mount user1 as /mnt/user and then mount /documents as /mnt/documents the data from the last subvolume mounted shows in both mounts. Mount also shows: 172.16.0.28:/documents/ on /mnt/user type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.0.28,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=172.16.0.28) 172.16.0.28:/documents/ on /mnt/documents type nfs (rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=...

...uction for a while now quite successfully but we are finding that our Windows clients are having their rates limited to ~1 Gbps despite having 10 Gbit interfaces (iperf tests show a 4.18 Gbps network speed). We can achieve far higher transfer rates when using Linux clients by setting the "wsize" and "rsize" mount.cifs options (we find that 8MB works well) but we've been unable to find an equivalent option for our Windows clients as there doesn't seem to be an option to specify how much the data will be sent in 1 SMB request. When inspecting the logs (as well as...

...sockaddr *)&sin, sizeof(*sin))) != -1) + if ((ret = bind(sd, (struct sockaddr *)sin, sizeof(*sin))) != -1) break; if (port == END_PORT) port = START_PORT; mango:~ # strace -f /lib/klibc/bin/nfsmount -o udp,rsize=8192,wsize=8192 192.168.1.2:/nfsroot/mango /mnt execve("/lib/klibc/bin/nfsmount", ["/lib/klibc/bin/nfsmount", "-o", "udp,rsize=8192,wsize=8192", "192.168.1.2:/nfsroot/mango", "/mnt"], [/* 46 vars */]) = 0 gettimeofday({1073419650, 154920}, NULL) = 0...

I can't explain why 700 msecs aren't enough to avoid timeouts in 100 Mbps networks, but my tests verify it, so I'm writing to the list to request that you increase the default timeo to at least 30, or to 600 which is the default for `mount -t nfs`. How to reproduce: 1) Cabling: server <=> 100 Mbps switch <=> client Alternatively, one can use a 1000 Mbps switch and