Message-ID: <4F71E29B.70106@cea.fr>
Date: Tue, 27 Mar 2012 17:54:03 +0200
From: DENIEL Philippe <philippe.deniel@cea.fr>
MIME-Version: 1.0
To: NFS list <linux-nfs@vger.kernel.org>
Subject: Client says "Stale NFS file handle" but server does not return NFS3ERR_STALE
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Sender: linux-nfs-owner@vger.kernel.org

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