Date: Sun, 29 Oct 2017 13:13:31 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Yuri Pankov <yuripv@gmx.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: NFSv3 issues with latest -current Message-ID: <YTOPR0101MB2172093DDDCB04687D83DA49DD580@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <9ceeafa5-cb7f-cb82-db07-de6f28b209e2@gmx.com> References: <9ceeafa5-cb7f-cb82-db07-de6f28b209e2@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yuri Pankov wrote: > All file operations (e.g. copying the file over NFSv3 for me) seem to be > stuck running the latest -current (r325100). Reverting just the kernel > to r323779 (arbitrary chosen) seems to help. I noticed the "Stale file > handle when mounting nfs" message but I don't get the "stale file > handle" messages from mount, probably as I'm not running any linux client= s. These kinds of problems are usually related to your net interface device driver or the TCP stack. A couple of things to try: - Disable TSO (look for a sysctl with "tso" in it). - Try using mount options rsize=3D32768,waize=3D32768 to reduce the I/O size. Some device drivers don't handle long chains of mbufs well, especially when the size is near 64K. (These issues have been fixed in current, but if a bug slips into a net dri= ver update or ???) - Look at recent changes to the net device driver you are using and try rev= erting those changes if you can do so. - Capture packets and look at them in wireshark (which knows NFS) and see what is going on the wire. There hasn't been any recent changes to NFS that should affect NFSv3 mounts or to the kernel rpc, so I doubt the NFSv4.1 changes would be involved. rick=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB2172093DDDCB04687D83DA49DD580>