Sometimes Test-18/20 fails from: ./tests/bugs/quota/bug-1087198.t Test-18 TEST grep -e "\"Usage crossed soft limit:.*used by /$QUOTA_LIMIT_DIR\"" -- $BRICK_LOG_DIR/* Test-20 TEST grep -e "\"Usage crossed soft limit:.*used by /\"" -- $BRICK_LOG_DIR/* Problem is. Consider below scenario in the quota xlator. T1 - write with delta1 bytes on fd1 check_limit sees that delta1 bytes is not exceeding soft limit T2 - write with delta2 bytes on fd1 check_limit sees that delta2 bytes is not exceeding soft limit T3 - delta1 and delta2 bytes are written to the disk. Here delta1 and delta2 are checked separately and do not exceed limit, but they together exceed the limit which is not checked.
REVIEW: http://review.gluster.org/9894 (remove spurious failure test from bug-1087198.t) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
Note: In Patch# 9894 Test-18 and 20 are commented in test './tests/bugs/quota/bug-1087198.t'. These should be un-commented once the actual problem is solved.
COMMIT: http://review.gluster.org/9894 committed in master by Vijay Bellur (vbellur) ------ commit 71210c021f7b6d7b79f31553d7bd8632d1f6e99f Author: vmallika <vmallika> Date: Mon Mar 16 15:38:16 2015 +0530 remove spurious failure test from bug-1087198.t Consider below scenario in the quota xlator T1 - write with delta1 bytes on fd1 check_limit sees that delta1 bytes is not exceeding soft limit T2 - write with delta2 bytes on fd1 check_limit sees that delta2 bytes is not exceeding soft limit T3 - delta1 and delta2 bytes are written to the disk. Here delta1 and delta2 are checked separately and do not exceed limit, but they together exceed the limit which is not checked. We need to find a solution to solve this problem. Till then for other regressions to pass, we remove the the test which checks for soft limit crossed. Change-Id: I8f76754e975c3315557a4c570db8bb5d9e56de15 BUG: 1202292 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/9894 Reviewed-by: Atin Mukherjee <amukherj> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user