From owner-freebsd-current@freebsd.org Sun Oct 29 15:25:37 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B5C5E4241E for ; Sun, 29 Oct 2017 15:25:37 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 014BA816D9 for ; Sun, 29 Oct 2017 15:25:36 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id 8pSweNtUrI8mC8pSxeyjqd; Sun, 29 Oct 2017 09:25:35 -0600 X-Authority-Analysis: v=2.2 cv=HahkdmM8 c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=02M-m0pO-4AA:10 a=UqCG9HQmAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=ZGY0H6mgxZpHxj-iRFQA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id DCD66B5; Sun, 29 Oct 2017 08:25:33 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id v9TFPXmQ052790; Sun, 29 Oct 2017 08:25:33 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201710291525.v9TFPXmQ052790@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Rick Macklem cc: Yuri Pankov , freebsd-current Subject: Re: NFSv3 issues with latest -current In-Reply-To: Message from Rick Macklem of "Sun, 29 Oct 2017 13:13:31 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Oct 2017 08:25:33 -0700 X-CMAE-Envelope: MS4wfPFXRzdPTdydcPWSGgFXvr6cbg01t7F08XA2JZPFTz5P3ywwgtczv32f2MbYl3xAGDEZwv1GUjZvOLdUCGoWhXh0hs4aJoK3qKQC55q0XlZK7bshih6o 6bHswOGtuMzJqdFRkPiRXFu6dWsEmjnwk7HNmY2ACCPHJ3kAFqIBvGpoihP/qlqnUealfKZGRhXqF65yX5V9ZO8/NcxM2dOgXt7gQuOt8IA9EVh6VIoDn9Yc v7HvKtst0sVol1/PwocB/A== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 15:25:37 -0000 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 mounting nfs" message but I don't get the "stale file > > handle" messages from mount, probably as I'm not running any linux clients. > 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). The sysctl is net.inet.tcp.tso. You can also disable tso through ifconfig for an interface. Additionally, though not directly related to this, TSO is not generally firewall friendly either. Our friends at pfsense document it be disabled. It can cause issues with our ipfilter firewall on some interfaces (e.g. fxp). I also recall reading a Juniper KB about path MTU discovery and TSO not playing well together. Not that TSO is bad but disabling it is something to try when diagnosing network problems. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.