Description of problem: set the quota limit started creating data in nfs.log there are loads of waring messages. Version-Release number of selected component (if applicable): glusterfs-3.4.0.34rhs-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. create and start a volume 2. enable and set quota limit of 1GB on "/" 3. mount over nfs on a client 4. start creating data inside the mount-point Actual results: there are many Warning messages for a single itself, after quota limit is reached. Example, [2013-10-11 16:36:29.380171] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 15f4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.380258] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 15f4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.383242] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 16f4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.383278] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 16f4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.386541] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 17f4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.386577] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 17f4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.389726] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 18f4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.389782] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 18f4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.392957] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 19f4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.393037] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 19f4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.396236] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 1af4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.396273] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 1af4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.399489] W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 1bf4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.399525] W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3: XID: 1bf4dce6, WRITE: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), count: 0, UNSTABLE,wverf: 1381508849 [2013-10-11 16:36:29.400156] W [nfs3.c:4952:nfs3svc_commit_cbk] 0-nfs: 1cf4dce6: /f.195 => -1 (Disk quota exceeded) [2013-10-11 16:36:29.400196] W [nfs3-helpers.c:3504:nfs3_log_commit_res] 0-nfs-nfsv3: XID: 1cf4dce6, COMMIT: NFS: 69(Resource (quota) hard limit exceeded), POSIX: 122(Disk quota exceeded), wverf: 1381508849 Expected results: we shouldn't be sending many warning message for each single file. Additional info:
Per discusion with Shanks/Saurabh, removing this from the list
Per discussion with Amar, Expected behaviour as every file which is quota failed needs to be logged.
How is this "NOTABUG"? The issue mentioned is for single file itself having many warning messages If you wish to have many warning message, rather move it to some other log level. Re-opening this BZ for further discussion.
needinfo based on https://bugzilla.redhat.com/show_bug.cgi?id=1018170#c4
NFS logs warning message logged twice in the FOP callback function. We can remove one log message.
http://review.gluster.org/11936
Patch upstream master : http://review.gluster.org/11936 Release-3.7 : http://review.gluster.org/12162
Bug verified on build glusterfs-3.7.5-6.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html