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
