search for: timeo

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

...//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. > > Now they cause the lags/timeouts that I reported. > > So please, instead of increasing...

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. Now they cause the lags/timeouts that I reported. So please, instead of increasing timeo, decrease the default rsize/w...

I managed to get to the bottom of this, and filed a bug report for NFS: https://bugzilla.kernel.org/show_bug.cgi?id=204939 Klibc nfsmount still a bug: it needs to NOT hardcode timeo=7. Either the NFS defaults should be used, which result in: timeo=600,rsize=1048576,wsize=1048576, or at least the kernel documented defaults, https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt which are: timeo=7,rsize=4096,wsize=4096 But clearly hardcoding (the old) timeo=7 and...

...6783e7a10fb7a638bc6034e4cdcb6296cea6a1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 17:18:41 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 7 Oct 2019 17:27:49 +0100 [klibc] nfsmount: Use kernel client's default value for timeo option The current default of timeo=7 (0.7 seconds) is too short, especially on slow networks. We should not override the kernel client's default unless explicitly requested. This option is passed to the kernel through struct nfs_mount_data rather than as a string, so we have to provide some...

...;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 10.1.50.2:/& tw...

Hi, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10 node.session.err_timeo.reset_timeout = 30 node.session.iscsi.InitialR2T = No node.session.iscsi.ImmediateData = Yes node.session.iscsi.FirstBurstLength = 262144 node.session.iscsi.MaxBurstLength = 16776192 node.session.iscsi.Defaul...

...val 30 ClientAliveCountMax 3 The ssh client kept hanging even after the network was resumed. It finally timed out after about 2 hours because the tcp_keepalive_time is set as 2 hours in sysctl. I looked at the ssh code downloaded from your website and found the Alive options are only used to setup timeout after ssh_session starts. So my question is why we do not start monitoring the liveness of ssh server right after a connection is established. It is annoying when an application relies on ssh to do periodic work but an occasional network failure causes the application to miss several service circ...

...#include <xenbus.h> #include <xenstore.h> +#include <poll.h> #include <sys/types.h> #include <sys/unistd.h> @@ -678,6 +679,29 @@ static void dump_set(int nfds, fd_set *readfds, fd_set *writefds, fd_set *except #define dump_set(nfds, readfds, writefds, exceptfds, timeout) #endif +#ifdef LIBC_DEBUG +static void dump_pollfds(struct pollfd *pfd, int nfds, int timeout) +{ + int i, comma, fd; + + printk("["); + comma = 0; + for (i = 0; i < nfds; i++) { + fd = pfd[i].fd; + if (comma) + printk(", "); +...

Hi, In a discussion on the kernel bugzilla (bug 11154) the question of NFS mount options came up. Trond Myklebust seems to consider the default nfsmount options (V3 over TCP, with timeo=7 and retrans=3) to be bad. I don't know yet if that's my problem, but anyway, would you consider changing the defaults to timeo=600 and retrans=2, if only just to match the default util-linux mount options ? Cheers, -- Michel "Walken" Lespinasse A program is never fully debugg...

...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=2,sec=sys,mountaddr=172.16.0.28,mountve...

...ther 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/wsize, use tcp protocol and change...

...ards - the one in use is connected to a PowerConnect 2216 10/100 switch and has negotiated 100Mbit. I''ll check if the stock Cambridge isn''t negotiating full duplex but that shouldn''t cause lockups. My mount options are: defaults,intr,rsize=32768,wsize=32768,nfsvers=3,tcp,timeo=600 This isn''t at NetApp (no 100Mbit there), but these are the options used by all their linux NFS clients. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...02 2.6.32-431.el6.x86_64), the storage - CentOS 6.4 also built-in drivers (Linux stor1.colocat.ru 2.6.32-279.el6.x86_64). On the storage is made an array, that is shown in system as /storage/s01. Then it is exported via NFS. The nodes connect to NFS by: /bin/mount -t nfs -o rdma,port=20049,rw,hard,timeo=600,retrans=5,async,nfsvers=3,intr 192.168.1.1:/storage/s01 /home/storage/sata/01 mount shows: 192.168.1.1:/storage/s01 on /home/storage/sata/01 type nfs (rw,rdma,port=20049,hard,timeo=600,retrans=5,nfsvers=3,intr,addr=192.168.1.1) Then we create a virtual machine with virsh with a disk bus virtio...

On 21 Sep 2020, at 01:48, Claudio Corvino <ccorvino at trustitalia.it> wrote: > problem still occurring, I just noticed that if I do an "ls -l /mnt/mail-storage/<user>/Maildir/cur/" from the Dovecot server I can unblock the mailbox of the user and Thunderbird can receives all the e-mails. > > The problem occurs even with the gmail client on the smartphone. >

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

...share just to check MWI, all read-write functions to the VM files > occur on the VM server only. > > On the registration servers, I mounted the remote VM share with this > in my fstab.conf: > > 10.10.14.124:/var/spool/asterisk/voicemail /mnt/vmserver nfs > soft,nolock,timeo=1,retrans=1,bg,intr > > all on one line of course > > [10.10.14.124:/var/spool/asterisk/voicemail] is the voicemail server > and [/mn/vmserver] is the mounted location, [nfs] is the file system > type, > > options: (the important stuff) > [soft] If an NFS file operati...

...be automatically mounted at boot time (unless I put in the 'noauto' option). But my NFS partition isn't getting mounted, here's the excerpt from my /etc/fstab file, split on the whitespace so it's easier to read: nfs_server:/exports/var/www /var/www nfs rsize=8192,wsize=8192,timeo=14,intr After the server comes up, I can do a simple, 'mount -a' and the partition is alive. Do I need to use something like autofs? I figured I wouldn't need that since there's no reason to unmount this partition. Thanks, Ajay

...t sure why readlink is used in this case. This is a regular file and not a symlink. I hope you have some suggestions on how to debug this further. Details on the servers's file systems: Server backupserver: /data is mounted like this: nfs:/data/nfs/nfs0/data/xx/backup on /data type nfs (rw,timeo=60,intr,rsize=16384,wsize=16384,addr=78.xx.xx.xx) Server mailserver: /data is mounted like this: nfs:/data/nfs/nfs0/data/xx/mail on /data type nfs (rw,timeo=60,intr,rsize=16384,wsize=16384,addr=78.xx.xx.xx) Med venlig hilsen/Kind regards Thomas Damgaard Nielsen http://thomasdamgaard.dk

....2.1 one week ago,and replication 2 server. OS:CentOS5.5 64bit RPM:glusterfs-core-3.2.1-1 glusterfs-fuse-3.2.1-1 command gluster volume create syncdata replica 2 transport tcp 172.23.0.1:/home/syncdata 172.23.0.2:/home/syncdata mount command 172.23.0.1 -> mount -t glusterfs -o tcp,soft,timeo=3 172.23.0.1:/syncdata /syncdata 172.23.0.2 -> mount -t glusterfs -o tcp,soft,timeo=3 172.23.0.2:/syncdata /syncdata So,Yesterday I update GlusterFS to 3.2.2-1 and use nfs mount. 172.23.0.2 -> mount -t nfs -o nolock,nfsvers=3,tcp,hard,intr 172.23.0.2:/syncdata /syncdata [root at 172.23.0...