Description of problem: NFS Duplicate Reply cache feature should provide proper debugging messages with the reason of the failure in nfs log file when the NFS server could not cache the duplicate request message or could not send the cached reply for some reason. Version-Release number of selected component (if applicable): [root@localhost ~]# rpm -qa | grep glusterfs glusterfs-api-3.4.0.52rhs-1.el6rhs.x86_64 glusterfs-libs-3.4.0.52rhs-1.el6rhs.x86_64 glusterfs-geo-replication-3.4.0.52rhs-1.el6rhs.x86_64 samba-glusterfs-3.6.9-167.8.el6rhs.x86_64 glusterfs-3.4.0.52rhs-1.el6rhs.x86_64 glusterfs-server-3.4.0.52rhs-1.el6rhs.x86_64 glusterfs-rdma-3.4.0.52rhs-1.el6rhs.x86_64 glusterfs-fuse-3.4.0.52rhs-1.el6rhs.x86_64 [root@localhost ~]# How reproducible: Steps to Reproduce: 1. create a 6x2 volume, start it 2. mount over nfs, create 10 directories 3. set limit of 1TB on root of the volume and 10GB on each directory 4. start creating data inside each directory. Actual results: The following error messages appears in the nfs.log [2013-12-19 21:40:01.826319] E [rpc-drc.c:499:rpcsvc_add_op_to_cache] 0-rpc-service: DRC failed to detect duplicates Expected results: The error message "DRC failed to detect duplicates" doesnot give any information about failure reason which is blocking our automation to proceed. Additional info: This is a test/automation blocker. Refer- Bug 1045271
Newer versions of RH(G)S have DRC disabled by default due to instability issues. We are currently not planning to resolve these issues in Gluster/NFS. When progress is made in upstream bug 1105883, we can revisit this decision.