From owner-freebsd-fs@freebsd.org Tue Feb 27 19:39:36 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE177F215A5 for ; Tue, 27 Feb 2018 19:39:35 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.187.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 639A06BB19; Tue, 27 Feb 2018 19:39:35 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id EBCD9201BF; Tue, 27 Feb 2018 20:39:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519760368; bh=i5e69zb46byA0Kg4gwIj2bq8AE63oL776leDOHZHnmY=; h=To:Cc:From:Subject:Date; b=rXqVmkLmVN940fOCWd0x3JwxNvbYWEu7rsNBI1QEmZkH9l+6FSj1L6csFqjzOvSnU rqWJPNxmMgyGxUrMNEE+aeDklzSkR9nwHZLn3dKfK766hNvPBVL+mp+wJJpxDLy1GQ kjXrAwPV3xRwtUdpG/4HZvhd1YF312laJukFjYmWAvTGgoT+v3YbG24pw7XjSf95U/ +fRRqL+L7VqGoVk3R+IsOuZOMe0FgwBw025UHAOi6KNGgZgQ3gGHByaQEe1FmvvWPm GV7S7djJOXb9gjsI4AQv6KyGkWrarz2LC72mlQIgsgUWNIwOqdUWs4bV8tIXNQvE8N P/zg7eRxZ6/CSrUKAXIaHAB8641GnOFQEtANJ4919Rd0l8seDUOU8wCdrzVpxqS2SF uygdvmXi1Y3kATZ60M1v4crH9gH0M6P1bCFl3tJ6wyfIt+C6HPmxeSDw75EOenmQuO M4PVV9jR2TWuHWVK7OXp8DlwZkJDMLWKzuZRzsD6IkzXWMcNAh556TiCI4wdcTyLSQ 327bOPAgGKbMkrwSHO/ZM7caccuiXhF/sLg8/FtJPlM6TFCXa0SwnvfVuOGIoHcBxN u93ni6Ek9UZDpHUj2EKmZMZo8M4oBJhwveisMTFFEWmn+Oefy97t8Rz7A1wWhbfiYx 8PMsIh6x+vTEl1mEaZbY+fo8= Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 54968201AE; Tue, 27 Feb 2018 20:39:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1519760365; bh=i5e69zb46byA0Kg4gwIj2bq8AE63oL776leDOHZHnmY=; h=To:Cc:From:Subject:Date; b=jn3qSZBZH69kVQQ12M7fjUP0zKPoly1RMDoFMMog80w9HInx3lDxb7qZgpxaa3CZb x9lAsU2iuNlD5v0C2q7daYwGKBtUn+prQjPVz1/eLzUmx8Jg3hobvR+QssueGt0B4g rqALuvwiPmlGPsFx6jWBmXFYZoDPx/q8FvCqQNUCjiuZ0xJI5nTMlXJ03VLIAw59hV 6ZgCqpdHGzkifXjDzw+frACJVu+WHv+HqP2/GueOeTv1Lb8PFhHb7rO3sjahATM0Dq bZDq1prm2RIpzJa/oqwTXK+u8eYJENFO03IqlqOQmfefuHZq3QMpbBytbo40s20EoJ EnCbRSUDvrUb/3X5p+8u1Hx5y+QU5JYMskuqE2sqhqAOw+ynJBGg9xPuusaz9I5xFw ozko33VEIvT7XLcAJzzC76fe+n5HXh/7qFz1joyE7MZZr/XXA+mrZKXctSEwiiqd0b h984VwsGhlwbO32vJO0Jz5RkWatNtZ7ZATKDV7EtR+iKnO2IldfxxNkB9zJ1myXxAq 6COd7ZmSF8s+Ic4E+aPME9LqXXglLyqKi0U9Bz0kNwaDltFFwyZ7PQDZDOE1LpCS1H 5MrvMCaFkPv/JRP7kt5+3uKJX6lBRg30atLM+67o9rN1Dq5umMzxXVZmHwzHpsTcAM lvB5evvEwGuVPSZll+nOjhxY= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vm1982.vellance.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.1 Received: from rubens-MacBook-Air.local (ip51ccb320.speed.planet.nl [81.204.179.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA; Tue, 27 Feb 2018 20:39:22 +0100 (CET) To: freebsd-fs@freebsd.org Cc: rmacklem@FreeBSD.org From: Ruben Subject: Linux NFSv4 clients: bad sequence-id errors. Message-ID: Date: Tue, 27 Feb 2018 20:39:21 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 19:39:36 -0000 Hi List, I'm experiencing a strange issue on a machine providing a couple of nfsv4 exports. A Linux client that generates a lot of traffic to and from the nfs server sometimes starts throwing "bad sequence-id errors": Feb 27 10:39:42 localhost kernel: [12481477.608103] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 80f7d0d0! They typically occur after a couple of months of uptime on the nfsd machine. Every couple of seconds they are thrown by the client. The situation is "remedied" by restarting the nfsd on the server. Although functionality on the specific client does not appear to be affected (much?), its a bit disturbing. I've done some digging and found : https://lists.freebsd.org/pipermail/freebsd-fs/2015-July/021707.html and the patch attached by Rick (  nfsv41exch.patch : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20150729/586f776a/attachment.bin ) . Since the issue started manifesting itself I have restarted the nfs daemon (grabbed a pcap and the corresponding error lines mentioning the sequences prior to doing that in case anyone is interested). The nfs server runs FreeBSD 11.1 : freebsd-version -uk 11.1-RELEASE-p1 11.1-RELEASE-p1 but I have seen it on 10.2 and 11.0 as well. The linux client is (/has been) running a version of Debian. The export lines in /etc/exports : V4: / -network=192.168.9.0 -mask=255.255.255.0 /data/Sabnzb2015 -maproot=root: -alldirs -network=192.168.9.0 -mask=255.255.255.0 Uptime: 8:27PM  up 196 days, 22:10, 1 users, load averages: 0.21, 0.17, 0.17 Traffice since uptime (guessing NFS / non-NFS ratio of 3 to 1)           lagg0  in    400.901 KB/s        400.901 KB/s           10.425 TB                  out    32.781 KB/s         32.781 KB/s           14.132 TB I'm wondering: can the 2015 patch provided by Rick still be "safely" applied or has the nfs code changed too much since then? I've witnessed this issue a couple of times now and would very much like to test the patch provided. Kind regards, Ruben