Date: Sat, 5 Mar 2016 17:24:26 +0300 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: FreeBSD Stable ML <stable@freebsd.org> Subject: Re: nfs_getpages: error 4 Message-ID: <9BBCBDD0-4DAD-4189-9AAA-9FD94A458F7E@gmail.com> In-Reply-To: <56DAE6D2.5040309@grosbein.net> References: <A2A32332-4D9D-40DF-9DEC-EE9000879416@gmail.com> <56DACD4E.3070905@grosbein.net> <550ADE4F-9F60-44FB-BF07-A1384A6B7B1A@gmail.com> <56DAE033.9020304@grosbein.net> <ED06D277-F19B-46F4-BD61-08B6AD10326B@gmail.com> <56DAE6D2.5040309@grosbein.net>
index | next in thread | previous in thread | raw e-mail
> On 05 Mar 2016, at 17:01, Eugene Grosbein <eugen@grosbein.net> wrote: > > 05.03.2016 20:42, Dmitry Sivachenko пишет: > >>> and to discover what version is broken. And show full mount command/option set. >> I already included mount flags from fstab in my original e-mail: >> >> rw,bg,intr,soft > > If that's only options you use, there is another workaround: add options > rsize=1024,wsize=1024 to avoid possible packet reassemply/defragmentation > related bugs. I wonder how rsize=wsize=1024 will affect performance? I have 10GBit network and I expect to achieve comparable throughput. > > Again, error 4 is EINTR so you could disable both "soft" and "intr" options for test. "soft" is meaningless in such setup, because "file system calls will fail after retrycnt round trip timeout intervals" but "The default is a retry count of zero, which means to keep retrying forever". If I understand "intr" correctly, it matters only when server becomes unresponsive, that is "server is not responding" message should be in my logs. But I have no such a message. > Anyway, re-read mount_nfs(8) manual page, section BUGS before switch to NFSv4. That is why I chose to use NFSv3, I thought it is more mature and stable implementation.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9BBCBDD0-4DAD-4189-9AAA-9FD94A458F7E>