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

[bugzilla at redhat.com]

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

            Bug ID: 1229297
           Summary: [Quota] : Inode quota spurious failure
           Product: GlusterFS
           Version: mainline
         Component: quota
          Assignee: bugs at gluster.org
          Reporter: spandit at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.