[Bugs] [Bug 1242329] New: [Quota] : Inode quota spurious failure

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1242329

            Bug ID: 1242329
           Summary: [Quota] : Inode quota spurious failure
           Product: GlusterFS
           Version: 3.7.2
         Component: quota
          Severity: high
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: vmallika at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    spandit at redhat.com, vmallika at redhat.com
        Depends On: 1229297



+++ This bug was initially created as a clone of Bug #1229297 +++

I did some analysis on this and found out below mentioned
log during the case of failure.

[2015-06-08 03:45:21.317352] I [MSGID: 115071]
[server-rpc-fops.c:1591:server_crea
te_cbk] 0-patchy-server: 203: CREATE /test_dir/test1.txt
(72fa9c7d-d4cd-474e-baae-
28dde9b15990/test1.txt) ==> (Disk quota exceeded) [Disk quota exceeded]

The test case which fails is "TEST_IN_LOOP touch $M0/test_dir/test$i.txt",
while creating a file "test1" (i.e i=1). This should not fail as "test1" is
the first file being created in the directory where quota limit is set.
The only possible explanation is that before creating the file "test1",
we delete all the files present in that directory, and that information
has not been updated by marker. Because of which the new file creation
fails thinking the quota limit is still exceeded.

The test case basically validates both the types of quota (size and inode).
The reason for this spurious failure might be because of the delay in
updating the information my marker. I will verify the same by inducing
some delay before the execution of above mentioned testcase.

--- Additional comment from Anand Avati on 2015-06-08 08:13:40 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#1) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-09 01:08:33 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#2) for review on master by Vijay Bellur (vbellur at redhat.com)

--- Additional comment from Anand Avati on 2015-06-09 01:38:00 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#3) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-09 02:54:56 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#4) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-09 04:16:07 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#5) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-12 04:36:18 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#6) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-15 01:45:10 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#7) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-23 06:33:27 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#8) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-25 05:58:33 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#10) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-06-30 05:30:09 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#11) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-07-09 01:46:15 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#12) for review on master by Sachin Pandit (spandit at redhat.com)

--- Additional comment from Anand Avati on 2015-07-10 05:23:57 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#13) for review on master by Vijaikumar Mallikarjuna
(vmallika at redhat.com)

--- Additional comment from Anand Avati on 2015-07-11 23:25:43 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#14) for review on master by Vijaikumar Mallikarjuna
(vmallika at redhat.com)

--- Additional comment from Anand Avati on 2015-07-11 23:32:19 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#15) for review on master by Vijaikumar Mallikarjuna
(vmallika at redhat.com)

--- Additional comment from Anand Avati on 2015-07-12 11:44:22 EDT ---

REVIEW: http://review.gluster.org/11125 (features/quota : Fix spurious failure)
posted (#16) for review on master by Vijaikumar Mallikarjuna
(vmallika at redhat.com)

--- Additional comment from Anand Avati on 2015-07-13 00:34:59 EDT ---

COMMIT: http://review.gluster.org/11125 committed in master by Krishnan
Parthasarathi (kparthas at redhat.com) 
------
commit 46d4d7ade012f86044135dd4af3101f851484cda
Author: vmallika <vmallika at redhat.com>
Date:   Fri Jul 10 14:37:50 2015 +0530

    features/quota : Fix spurious failure

    Problem : Basically, in this test case a file is created
    which exceeds the quota limit. Once the limit is reached
    that file will be deleted. At the same moment we are
    testing inode-quota. It can so happen that before the
    marker updates the information related to deletion of
    file, a new file creation operation comes and sees that
    quota limit is still exceeded.

    Solution : Inducing a check to see if marker updation
    completed successfully.

    Updated all the test case which has the similar
    machanism and also moved the "usage" function
    to a common place "volume.rc"

    Change-Id: I36ddbc5ebbf1b74c9d326a0d1d5f3b32f20a906a
    BUG: 1229297
    Signed-off-by: Sachin Pandit <spandit at redhat.com>
    Signed-off-by: vmallika <vmallika at redhat.com>
    Reviewed-on: http://review.gluster.org/11125
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1229297
[Bug 1229297] [Quota] : Inode quota spurious failure
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.