Re: NFSv3 issues with latest -current

2017-10-31 Thread Yuri Pankov
On Wed, 1 Nov 2017 00:27:50 +, Rick Macklem wrote: Rodney W. Grimes wrote: [stuff snipped] I wrote: Btw, NFS often causes this because... - Typically TSO is limited to a 64K packet (including TCP/IP and MAC headers). - When NFS does reading/writing, it will do 64K + NFS, TCP/IP and MAC head

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] > I wrote: >> Btw, NFS often causes this because... >> - Typically TSO is limited to a 64K packet (including TCP/IP and MAC >> headers). >> - When NFS does reading/writing, it will do 64K + NFS, TCP/IP and MAC headers >> for an RPC (or a multiple of 64K li

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rodney W. Grimes
> Cy Schubert wrote: > [stuff snipped] > >The sysctl is net.inet.tcp.tso. You can also disable tso through ifconfig > >for an interface. > > > For testing this case, I'd recommend using the sysctl. Since the net device > driver is often the culprit, that device driver might not handle the > "ifcon

Re: NFSv3 issues with latest -current

2017-10-31 Thread Rick Macklem
Cy Schubert wrote: [stuff snipped] >The sysctl is net.inet.tcp.tso. You can also disable tso through ifconfig >for an interface. > For testing this case, I'd recommend using the sysctl. Since the net device driver is often the culprit, that device driver might not handle the "ifconfig" correctly ei

Re: NFSv3 issues with latest -current

2017-10-29 Thread Yuri Pankov
On Sun, 29 Oct 2017 18:11:41 +0300, Yuri Pankov wrote: On Sun, 29 Oct 2017 13:13:31 +, Rick Macklem wrote: 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 (arbitrar

Re: NFSv3 issues with latest -current

2017-10-29 Thread Cy Schubert
In message , Rick Macklem writes: > 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

Re: NFSv3 issues with latest -current

2017-10-29 Thread Yuri Pankov
On Sun, 29 Oct 2017 13:13:31 +, Rick Macklem wrote: 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 hand

Re: NFSv3 issues with latest -current

2017-10-29 Thread Rick Macklem
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 "

NFSv3 issues with latest -current

2017-10-29 Thread Yuri Pankov
Hi, 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