NFS4ERR_EXPIRED means the client is trying to use state that the server
believes to have expired or that has been supplanted by newer state.
Can we get kernel versions for the client and server? Have you talked
to your Red Hat support channel about this?
This capture doesn't appear to show any bugs or bad behaviors, but a
longer capture may..
Ben
On 2 Apr 2018, at 13:50, Orion Poplawski wrote:
I'm having a lot of trouble with NFS going out to lunch between my
RHEL7
machines. Users cannot access files, and get errors like:
$ touch blah
touch: cannot touch ‘blah’: Input/output error
I'm attaching a pcap trace of the above touch during the problem. It
seems
that the server is returning NFS4ERR_EXPIRED.
Reboots/restarts of nfs help for a bit but then the problems return.
Other symptoms of trouble are messages like:
RPC: fragment too large: 613351424
on the client.
Any help with trying to track this down would be greatly appreciated.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxx
Boulder, CO 80301 https://www.nwra.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
