Bug 1023149
Summary: | Quota limit set to higher value doesn't comes to effect after remove-brick | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | shylesh <shmohan> |
Component: | quota | Assignee: | Vijaikumar Mallikarjuna <vmallika> |
Status: | CLOSED WORKSFORME | QA Contact: | storage-qa-internal <storage-qa-internal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.1 | CC: | rhs-bugs, shmohan, smohan, spalai, storage-qa-internal, vagarwal, vbellur, vmallika |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-17 08:50:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
shylesh
2013-10-24 17:39:01 UTC
Tried to reproduce the issue. [root@vm1 dir2]# glusterfs --version glusterfs 3.4.0.56rhs built on Jan 10 2014 22:58:18 [root@vm1 ~]# gvi Volume Name: test1 Type: Distributed-Replicate Volume ID: 7c8fa6e4-3e43-4fe0-a30f-6e8c3b5e87b4 Status: Created Number of Bricks: 4 x 2 = 8 Transport-type: tcp Bricks: Brick1: 192.168.122.240:/brick1/1 Brick2: 192.168.122.240:/brick2/2 Brick3: 192.168.122.240:/brick1/3 Brick4: 192.168.122.240:/brick2/4 Brick5: 192.168.122.240:/brick1/5 Brick6: 192.168.122.240:/brick2/6 Brick7: 192.168.122.240:/brick1/7 Brick8: 192.168.122.240:/brick2/8 [root@vm1 test]# gluster volume quota test1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- /test 500.0MB 80% 0Bytes 500.0MB No No /root 500.0MB 80% 0Bytes 500.0MB No No Used the following script to create files [root@vm1 dir1]# for i in {1..600} ; do dd if=/dev/zero of=file$i bs=1MB count=1 ; done [root@vm1 dir1]# gluster volume quota test1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- /test 500.0MB 80% 572.5MB 0Bytes Yes Yes /root 500.0MB 80% 0Bytes 500.0MB No No [root@vm1 dir1]# gluster volume remove-brick test1 192.168.122.240:/brick1/7 192.168.122.240:/brick2/8 status Node Rebalanced-files size scanned failures skipped status run time in secs --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 298 284.2MB 600 0 0 completed 62.00 * set limit of test dir to 1GB [root@vm1 dir1]# gluster volume quota test1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- /test 1.0GB 80% 572.5MB 451.5MB No No /root 500.0MB 80% 0Bytes 500.0MB No No [root@vm1 dir1]# Created a directory /test/dir2 and created files under it. But it filled the directory quota limit completely without any error. [root@vm1 dir2]# gluster volume quota test1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- /test 1.0GB 80% 1.0GB 0Bytes Yes Yes /root 500.0MB 80% 0Bytes 500.0MB No No [root@vm1 dir2]# Shylesh can you verify the bug in latest build. Not able to re-create the problem as per comment# 3. Also 2.1 is EOL'ed, so closing the bug The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |