+++ This bug was initially created as a clone of Bug #1085254 +++ Description of problem: Once soft limit / hard limit is crossed, there are no "Alert" level logs indicating that usage is above soft-limit. The only log messages are ones similar to these: [2014-04-06 14:48:33.512884] I [server-rpc-fops.c:1447:server_writev_cbk] 0-test-vol-server: 634: WRITEV 0 (0f74aac5-eba2-4897-919a-6f8ada619a14) ==> (Disk quota exceeded) [2014-04-06 14:48:33.512979] I [server-rpc-fops.c:1447:server_writev_cbk] 0-test-vol-server: 635: WRITEV 0 (0f74aac5-eba2-4897-919a-6f8ada619a14) ==> (Disk quota exceeded) The alert message was seen only when the volume quota option "alert-time" was set to 0. How reproducible: Steps to Reproduce: 1. Create a volume, mount the volume and create a dir 2. Set limit on the dir for the volume 3. Add files using the mounted client, until quota limit set is exceeded. Actual results: No alert message Expected results: Messages are logged when the limit is crossed Additional info: The alert message is required for the Nagios log monitoring so that the Nagios volume service state can be changed when quota limits are crossed
REVIEW: http://review.gluster.org/7451 (feature/quota: Logging corrections) posted (#2) for review on master by Varun Shastry (vshastry)
REVIEW: http://review.gluster.org/7451 (feature/quota: Logging corrections) posted (#3) for review on master by Varun Shastry (vshastry)
REVIEW: http://review.gluster.org/7451 (feature/quota: Logging corrections) posted (#4) for review on master by Varun Shastry (vshastry)
The problem is that the updation of volume wide quota size happens only after soft-timeout/hard-timeout. Quota doesn't have the updated knowledge of the quota size until the cache is updated after the timeouts leading to not log. So, setting the timeouts to 0 makes quota keeps itself updated. gluster volume quota <volname> hard-timeout 0 gluster volume quota <volname> soft-timeout 0 gluster volume quota <volname> alert-time 0 <or-a-very-minimal-value-in-the-order-of-seconds>
COMMIT: http://review.gluster.org/7451 committed in master by Vijay Bellur (vbellur) ------ commit b00ef83d2b15594526b1c58ef944a7edaa7e9dfe Author: Varun Shastry <vshastry> Date: Fri Apr 11 17:31:32 2014 +0530 feature/quota: Logging corrections This patch solves the inconsistent quota usage logging when soft limit reached. Change-Id: I47e7f1e65ed4b8306a999a20cc8f6b1772d47627 BUG: 1087198 Signed-off-by: Varun Shastry <vshastry> Reviewed-on: http://review.gluster.org/7451 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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