[Bugs] [Bug 1324058] New: quota: check inode limits only when new file/dir is created and not with write FOP
bugzilla at redhat.com
bugzilla at redhat.com
Tue Apr 5 12:33:54 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1324058
Bug ID: 1324058
Summary: quota: check inode limits only when new file/dir is
created and not with write FOP
Product: GlusterFS
Version: 3.7.10
Component: quota
Assignee: bugs at gluster.org
Reporter: vmallika at redhat.com
CC: bugs at gluster.org
Depends On: 1323486
+++ This bug was initially created as a clone of Bug #1323486 +++
Below test-case fails with disk quota exceed even though there is space
available
1) create volume
2) # gluster volume quota vol1 limit-objects /test_dir 10
3) exceed inode limit. Create 9 files in loop ( test_dir alreday accounted as 1
inode used, we should be able to create another 9 files)
for i in {1..9}; do
touch /mnt/test_dir/f$i
done
Now if inode limit is full, but we have not set any usage limit. so any write
operation on the existing files should work, but fails with disk quota
exceeded.
dd if=/dev/zero of=/mnt/test_dir/f1 bs=256k count=4 oflag=sync
write failed: Disk quota exceeded
--- Additional comment from Vijay Bellur on 2016-04-05 08:31:45 EDT ---
REVIEW: http://review.gluster.org/13911 (quota: check inode limits only when
new file/dir is created) posted (#1) for review on master by Vijaikumar
Mallikarjuna (vmallika at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1323486
[Bug 1323486] quota: check inode limits only when new file/dir is created
and not with write FOP
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list