From: Jon Hunter <jonathanh@nvidia.com>
To: NeilBrown <neilb@suse.de>, Steven Price <steven.price@arm.com>
Cc: Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
linux-nfs@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] nfs: simplify and guarantee owner uniqueness.
Date: Thu, 19 Sep 2024 07:38:57 +0100 [thread overview]
Message-ID: <c98e8af5-f50c-49e4-8ced-0795ebcd2fbb@nvidia.com> (raw)
In-Reply-To: <172652955677.17050.4744720185342907808@noble.neil.brown.name>
Hi Neil,
On 17/09/2024 00:32, NeilBrown wrote:
> On Tue, 17 Sep 2024, Steven Price wrote:
>>
>> Hi Neil,
>>
>> I'm seeing issues on a test board using an NFS root which I've bisected
>> to this commit in linux-next. The kernel spits out many errors of the form:
>>
>> [ 7.478995] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.599462] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.600570] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.615243] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.636756] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.644808] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.653605] NFS: v4 server <ip> returned a bad sequence-id error!
>> [ 7.692836] NFS: nfs4_reclaim_open_state: unhandled error -10026
>> [ 7.699573] NFSv4: state recovery failed for open file
>> arm-linux-gnueabihf/libgpg-error.so.0.29.0, error = -10026
>> [ 7.711055] NFSv4: state recovery failed for open file
>> arm-linux-gnueabihf/libgpg-error.so.0.29.0, error = -10026
>>
>> (with the filename obviously varying)
>>
>> The NFS server is a standard Debian 12 system.
>>
>> Any ideas?
>
> Not immediately. It appears that when the client opens a file during
> recovery, the server doesn't like the seqid that it uses...
>
> Recover happens when the server restarts and when the client and server
> have been out of contact for an extended period or time (>90 seconds by
> default).
> Was either of those the case here? Which one?
I am seeing various failures on -next and bisect is also pointing to
this commit. Reverting it does fix these issues. On one board I also
observed ...
[ 12.674296] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 12.780476] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 12.829071] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 12.971432] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 13.102700] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 13.171315] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 13.216019] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 13.273610] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
[ 13.298471] NFS: v4 server 192.168.99.1 returned a bad sequence-id error!
And on the same board I see ...
[ 16.496417] NFS: nfs4_reclaim_open_state: unhandled error -10026
[ 16.991736] NFS: nfs4_reclaim_open_state: unhandled error -10026
[ 17.106226] NFS: nfs4_reclaim_open_state: unhandled error -10026
Jon
--
nvpublic
next parent reply other threads:[~2024-09-19 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172558992310.4433.1385243627662249022@noble.neil.brown.name>
[not found] ` <5c90c3d0-c51f-4012-9ab6-408d023570c8@arm.com>
[not found] ` <172652955677.17050.4744720185342907808@noble.neil.brown.name>
2024-09-19 6:38 ` Jon Hunter [this message]
[not found] <1d66e015-1ca7-4786-893c-9224ad0c7371@arm.com>
[not found] ` <172680136351.17050.10296437171546281772@noble.neil.brown.name>
2024-09-22 12:56 ` [PATCH] nfs: simplify and guarantee owner uniqueness Jon Hunter
2024-09-22 23:21 ` NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c98e8af5-f50c-49e4-8ced-0795ebcd2fbb@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=anna@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=neilb@suse.de \
--cc=steven.price@arm.com \
--cc=trondmy@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).