Bryan Schumaker <bjschuma@...> writes: > > On Tue, Nov 15, 2011 at 04:48:57PM -0500, Bryan Schumaker wrote: > > > > Sorry, I'm having trouble keeping up.... What exactly do you do, on > > which machine, and what do you then see happen? > > Here is what I'm doing (On debian with 2.6.32): > - (On Client) Mount the server: `sudo mount -o vers=3 > 192.168.122.202:/home/bjschuma /mnt` > - (On Client) Lock a file using nfs-utils/tools/locktest: `./testlk > /mnt/test` > - (On Server) Call sm-notify with the server's IP address: `sudo > sm-notify -f -v 192.168.122.202` > - dmesg on the client has this message: > lockd: spurious grace period reject?! > lockd: failed to reclaim lock for pid 2099 (errno -37, status 4) > - (In wireshark) The client sends a lock request with the "Reclaim" bit > set to "yes" but the server replies with "NLM_DENIED_GRACE_PERIOD". > > Shouldn't the server be allowing the lock reclaim? When I tried > yesterday using 3.0 it only triggered DNS packets, I tried again a few > minutes ago and got the same results that I did using .32. > > - Bryan > Yes, everything is exactly as you wrote. After the steps above I also get the following in client logs: lockd: server in grace period lockd: spurious grace period reject?! lockd: failed to reclaim lock for pid 2508 (errno -37, status 4) Thank you all for taking time! -- 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
