Hello list,
We have a problem with the NFS client on Linux on a NetApp filer. Every
now and then we are getting huge amounts of "Remote IO Errors" on the
mounted home directories. This is new, we had no problems with the same
setup some months ago.
The reason for the Remote IO Errors is that the server is returning an
NFS4ERR_RESOURCE error, even just for
a simple "touch foo". The tcpdump of such a touch command I have listed
below.
I suspect that maybe the deduplication or backup operation make the
filer "busy" so it cannot respond to all compound operations.
I've seen that linux NFS just passes this error to the user as
EREMOTEIO. OpenSolaris seems to delay and retry. According to the RFC
I'm not sure what would be the right thing to do. But I think this is
meant to be a temporary error, and an NFS client should, in the example
below, take the first two operations as completed, and retry the
remaining 5 ones, or maybe retry the whole compound message.
What is your insight on this error ?
Is there something I can try, like returning EAGAIN and see if the error
gets handled correctly ?
The problem ocurred one or twice a week, without any regularity..
Thanks for your help
André
"touch foo" request from the client:
==================
NFS V4 COMPOUND Call PUTFH;SAVEFH;OPEN;GETFH;GETATTR;
RESTOREFH;GETATTR
Remote Procedure Call, Type:Call XID:0x00c46a7a
Network File System
[Program Version: 4]
[V4 Procedure: COMPOUND (1)]
Tag: <EMPTY>
length: 0
contents: <EMPTY>
minorversion: 0
Operations (count: 7)
Opcode: PUTFH (22)
Opcode: SAVEFH (32)
Opcode: OPEN (18)
Opcode: GETFH (10)
Opcode: GETATTR (9)
Opcode: RESTOREFH (31)
Opcode: GETATTR (9)
==================
Error Response from the server:
==================
NFS V4 COMPOUND Reply PUTFH;SAVEFH;OPEN
Remote Procedure Call, Type:Reply XID:0x00c46a7a
Network File System
[Program Version: 4]
[V4 Procedure: COMPOUND (1)]
Status: NFS4ERR_RESOURCE (10018)
Tag: <EMPTY>
length: 0
contents: <EMPTY>
Operations (count: 3)
Opcode: PUTFH (22)
Status: NFS4_OK (0)
Opcode: SAVEFH (32)
Status: NFS4_OK (0)
Opcode: OPEN (18)
Status: NFS4ERR_RESOURCE (10018)
==================
--
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
