More information:
if I do "echo 32767 > /proc/sys/sunrpc/nfs_debug", I can see this in syslog:
Mar 27 18:11:15 aury63 kernel: [32430.065930] NFS:
nfs_lookup_revalidate(/a) is invalid
Any Idea ?
Philippe
DENIEL Philippe a écrit :
Hi,
I have the following issue:
Client does a classical "mount -o vers=3,lock server:/path /mnt". The
server is my nfs-ganesha user space server.
Then, a long time running "dd if=/dev/zero of=./foo..." is made inside
a directory in the mount point. No matter what the other parameters of
dd (like bs= or count=) are : I kill the daemon, and restart it a
couple of seconds later. Then I kill the dd (CTRL-C from the console).
The dd command returns an error (which is logical, it' sis IO error or
Bad File Descriptor), but I see something else that is quite strange:
- if I ls from the current directory (where I ran 'dd'), I got the
message "ls: cannot open directory .: Stale NFS file handle"
- In wireshark, I see no NFS3ERR_STALE
The wireshark capture shows that the "server shutdown" was made
between a WRITE reply and the related COMMIT call (I received the
COMMIT call as the server rebooted).
Apparently, the client decided to return "Stale NFS file handle" to
the client, the server returns no error, all replies are NFS3_OK.
What should I be looking for to fix this bug ? (which is probably on
my side)
Regards
Philippe
--
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
--
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
