From owner-freebsd-current@freebsd.org Sun Oct 29 12:58:20 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 A2254E62D4A for ; Sun, 29 Oct 2017 12:58:20 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 05DF87CEF8 for ; Sun, 29 Oct 2017 12:58:19 +0000 (UTC) (envelope-from yuripv@gmx.com) Received: from [192.168.1.2] ([94.233.210.201]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0Lt1yI-1dBlKr1Nda-012WEx for ; Sun, 29 Oct 2017 13:52:59 +0100 To: freebsd-current From: Yuri Pankov Subject: NFSv3 issues with latest -current Message-ID: <9ceeafa5-cb7f-cb82-db07-de6f28b209e2@gmx.com> Date: Sun, 29 Oct 2017 15:53:00 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:2mKlomMpiX0Zjmg1REFvBZV2N4KR5KMIgDETiKAxhetD8e4PCco cd97iiYO0/05dhO8qyf9S2zks4nTXNcqVS3xlQrCM9vF0kmcPw7Dwn1+TsCYiAboh69tpB+ rEHrlAY7hXcu88cSQLYEb3yxgnXTeh6Sitr7rCMIoor88G7TMWJ3xxWsrYIiHBwLqNqbmvV E7xDp7EBMFEVX7HKszRTw== X-UI-Out-Filterresults: notjunk:1;V01:K0:wsQ+2CsLdv4=:uUYlgThyQmD2mfjtCeVDPO kjXF6dYXSXdpKnc11CYB3y7p5BqJkKBlyhCCK+PKfwch/Wj2k9RQmtYcgpR0SDhul6HX6DR5a sol1J9qCZMR41UFmSusQCIlf7kaL26J2dx2rcaIDs6O71CincjlinBGFWD3yDiV8x0Cf7BHvq z/zjr0WSTvOTi7ZctYaDyN0eeJSVnbe+gEmGCWU/CGj8s/fIqQn1pHMiZdiZkYloh4wh7cOOn 00fLoGpjxKzI2Hpy1gzWzvf0DLm4I7DD9Dp5ehW6b6JoThQ8Qsh9xr7aoDzoFlGr2+5O6VMpk KHmyNbY2IjSlcPoTfN6kqLTHYTLCUYXBb0HJsKHTJFPHt63SZm3j2nvTN33q0S/dljIJGX51t JictHyt1FPqH5sB23YhdBN2JRLzbAYmb2D492C6QqE2TfRT2ET3barpzzhIeZF5q+DSKcQ7Oe PvJLYXzgQ13yciynyTPa4xAG7InR4Lfljf4sUaWN+LVM6U7fklMJoGl7SLqf2oRW+y6zmpc6z npxDjNzldeUJ1YZj/2Y1Bay6xD91ExJiZ+4uyIQ6DHy+N+dIgoysXeOfqPnqhLQWsDK8Av2Qw 6SY905n9HpWKRlBIy8zrzJv2eYvPEswQKuuueff9NZVmwgo3u1hb3R6zRq7AAa9XKGAchYhuF GI4pcb0kG7iUhP/PDF4gVsCYqR9A5h4pB2VG3tIr++Wit83WtWl9dfesu500mK6K9L1XfZ9UU WQstB9EU6oScNle/SMZNewdRzC0fpM+fON/ymaUy6k6wKxjzDkaMkRRVxYp0SXUf0NypbNcGm A9IUeIO9uTSOyjD+iyo44Yy7M0gbVUYZTdaCoqzk3OzpeZ2cw8= 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 12:58:20 -0000 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" messages from mount, probably as I'm not running any linux clients. Is anyone else seeing the same? Is there any other information I need to provide here?