Bug 787365 - nfs:fdctx not valid in nfs.log
Summary: nfs:fdctx not valid in nfs.log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: locks
Version: pre-release
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
Assignee: Vivek Agarwal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-02-04 13:35 UTC by Saurabh
Modified: 2016-02-18 00:03 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:21:47 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Saurabh 2012-02-04 13:35:09 UTC
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:

Comment 1 Anand Avati 2012-02-14 18:25:35 UTC
CHANGE: http://review.gluster.com/2747 (nfs: avoid logging invalid fdctx in case of anonymous fds) merged in master by Vijay Bellur (vijay)

Comment 2 Anand Avati 2012-02-20 08:49:51 UTC
CHANGE: http://review.gluster.com/2754 (protocol/client: delete locks only for non-anonymous fds) merged in master by Vijay Bellur (vijay)


Note You need to log in before you can comment on or make changes to this bug.