Description of problem: getting fctx not valid kind of warnings in the nfs.log while executing "iozone -a" glimpse of the error, [2012-02-04 13:30:58.322397] W [client-lk.c:379:delete_granted_locks_owner] 0-dist-rep-client-0: fdctx not valid [2012-02-04 13:30:58.322732] W [client-lk.c:379:delete_granted_locks_owner] 0-dist-rep-client-1: fdctx not valid Version-Release number of selected component (if applicable): 330qa21 How reproducible: Steps to Reproduce: 1.nfs mount a dist-rep volume 2.start iozone -a 3.kill "nfs process on the server side" 4.start the killed process again Actual results: after step 3. the iozone halts.(expected) after step 4. , few seconds later the iozone resumes the execution(expected) nfs.log start showing the above mentioned error(unexpected) Expected results: Additional info:
CHANGE: http://review.gluster.com/2747 (nfs: avoid logging invalid fdctx in case of anonymous fds) merged in master by Vijay Bellur (vijay)
CHANGE: http://review.gluster.com/2754 (protocol/client: delete locks only for non-anonymous fds) merged in master by Vijay Bellur (vijay)