From owner-freebsd-current@freebsd.org Sun Oct 29 15:11:54 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 34A6DE40D52 for ; Sun, 29 Oct 2017 15:11:54 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A110980EB5; Sun, 29 Oct 2017 15:11:53 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from thor.xvoid.org ([94.233.210.201]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0LdIBN-1dQNbz3EMj-00iRQr; Sun, 29 Oct 2017 16:11:42 +0100 Subject: Re: NFSv3 issues with latest -current To: Rick Macklem , freebsd-current References: <9ceeafa5-cb7f-cb82-db07-de6f28b209e2@gmx.com> Cc: Stephen Hurd From: Yuri Pankov Message-ID: <790d22eb-e04d-3bc7-0e79-e01feedd4267@gmx.com> Date: Sun, 29 Oct 2017 18:11:41 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ZBFgtueJ6hfqsXaxui4WQaocF6nRuJi64YcJfkhqPh8GSYQaY0V D56CBgW/JomIo92DuXznlZFQhDZB7gejZqzlF2orhnMbIfmti0jw17YlRwXqi73WaZVUNkG I36VecyGkYxqMGjMlkrjY4JCydPjTZV1pLO5kzygZoLKqbh2WwzfMrHZTiOaennBY7a7G+p LFPkFHEL5K+126TAbbeXA== X-UI-Out-Filterresults: notjunk:1;V01:K0:rjepTLonuI0=:qXdAvBWzfztlDZUigA1w5M zQhFb5wWQvqTA+40cqte4+WfGQQKYmbvRlRqvG+lwYGb/sgV2R7Lv1xYmKwSRtOcddvPx/HSq FXv141FbuOH6j8I/KedswPVMY4tGdApJC0F5eC3AVfUX90DeTn6YZdTAmdv/Qqgb0F+PkD45y BVqpNJEPY7hQqfU4Pypbf1NS4eT077Mp84Hy9mXyZf+d826CvNt7fqSRC+h8ftQMoDoJ7B/xY +9wvcGDO9CUf9hscyQ1X5O1jNVpdirta6vvOsX/jchtNyat9WutlTKYLuxn4R1sKY6v79ZTil YJzYRSU9OzfwA1ug9Str5XQUtjH+bjOhKTWx3cLyifz8S52kyR27MUFFQ7gdUWxGm6MWcRMJH aw1wt5Y0w0mn2TVAUk2ekZCaR7wCrSha6ycFMKxF9DzM4FYFrZqIcOOzmthr7IIXxkJFrwp1a EvqQgSzzHYsHCYqgyv6al3YytfqSuI0PQgc4BP6sVloUP9cKKjAgpeQdCtJFK0GY1uMYn17h7 650jiD1zuncX8MGis5WBcN/EJYTGRQMH8+WRZgHxNG7jGRLkVbzIzvh4UceQQuQ/oc9+Hbfrg QyBC7X2bNpZ1lhpOjsNMhZGCGlwEa766U6fqVnak3WyqFwOCyvb6j/O1O66o5quWN9CkrsneA gtnpaXBC57sSXXSXy7mvQ+z/cdIMvBYR2eeS3GUib22M/n5owCRWZrRJbA9EIJzwNHUEmvTmB u4jDBksX7jVvGIYQN/zMbutW+EmRRoyiv3IpOlfQnnwJUdw1MTLMbWoXyEKIkFBzoaeWVY1pM k2pVnnznoofdLGcteLvk3U+H/FU8FOZFiYfDC5JxwHbbKdx5wrB4ZUncf6DpTHI9ApfhWwW2F XfRx+tj/NEg09JYeqt7ZEC0fm9rM38/C6B45iamxSS1y5F44GSJc4+bT6k59Gl 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:11:54 -0000 On Sun, 29 Oct 2017 13:13:31 +0000, 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 >> 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). > - Try using mount options rsize=32768,waize=32768 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 driver > update or ???) > - Look at recent changes to the net device driver you are using and try reverting > 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. Thanks for the hints, Rick! Indeed, it was one of the changes to sys/dev/e1000, reverting just the commit made everything look normal again (CC'ing the author). The NIC is: igb0@pci0:2:0:0: class=0x020000 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82576 Gigabit Network Connection' class = network subclass = ethernet Interface configuration (note the MTU): igb0: flags=8843 metric 0 mtu 9000 options=e525bb ether 00:25:90:72:54:22 inet6 fe80::225:90ff:fe72:5422%igb0 prefixlen 64 scopeid 0x1 inet 192.168.1.4 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active And the commit itself: commit f81cb8df32ae96299b8bbc2e948c17ad3aab59ca Author: shurd Date: Sat Sep 23 01:33:20 2017 +0000 Some small packet performance improvements If the packet is smaller than MTU, disable the TSO flags. Move TCP header parsing inside the IS_TSO?() test. Add a new IFLIB_NEED_ZERO_CSUM flag to indicate the checksums need to be zeroed before TX. Reviewed by: sbruno Approved by: sbruno (mentor) Sponsored by: Limelight Networks Differential Revision: https://reviews.freebsd.org/D12442 Notes: svn path=/head/; revision=323941