Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a volume with nfs.drc turned on, nfs.drc-size set to 8192. 2. Run ltp test on nfs client. Actual results: Wait for a while, "DRC failed to detect duplicates" keep printed in nfs.log. Expected results: Test run with no problem Additional info:
REVIEW: http://review.gluster.org/7519 (gNFS: gNFS drc cache failed to detecte duplicates.) posted (#1) for review on master by yuan ding (beback198611)
COMMIT: http://review.gluster.org/7519 committed in master by Anand Avati (avati) ------ commit 49733d307f010bfeb3d2440402ff51a5366262f5 Author: Yuan Ding <beback198611> Date: Mon Apr 21 22:10:13 2014 +0800 gNFS: gNFS drc cache failed to detecte duplicates. After the drc cache get full, message "DRC failed to detect duplicates" keep printed in the log. The root cause is drc_compare_reqs use the wrong compare type. This function should use type drc_cache_op_t as its input type. Since all rbtree related code (except function rpcsvc_drc_lookup) in drc cache pass drc_cache_op_t as compare type. Only rpcsvc_drc_lookup use type rpcsvc_request_t. It has been modified too. Change-Id: I925c097debe6b82f267986961fd4e7755f3de9af BUG: 1089676 Signed-off-by: Yuan Ding <beback198611> Reviewed-on: http://review.gluster.org/7519 Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Santosh Pradhan <spradhan> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users