Bug 1225738
| Summary: | [Quota] gluster v quota <volname> limit-usage should not accept any zero values | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anil Shah <ashah> | |
| Component: | quota | Assignee: | Manikandan <mselvaga> | |
| Status: | CLOSED NOTABUG | QA Contact: | storage-qa-internal <storage-qa-internal> | |
| Severity: | low | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.1 | CC: | ashah, mselvaga, rhs-bugs, smohan, storage-qa-internal, vmallika | |
| Target Milestone: | --- | Keywords: | EasyFix | |
| Target Release: | --- | Flags: | mselvaga:
needinfo-
|
|
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1241376 (view as bug list) | Environment: | ||
| Last Closed: | 2015-07-30 09:29:36 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1223636, 1241376 | |||
(In reply to Anil Shah from comment #0) > Description of problem: > > when you set limit-usage on root or sub-directory, if should not accept > zeros values. > > Version-Release number of selected component (if applicable): > > [root@darkknight ~]# rpm -qa | grep glusterfs > glusterfs-libs-3.7.0-2.el6rhs.x86_64 > glusterfs-cli-3.7.0-2.el6rhs.x86_64 > glusterfs-client-xlators-3.7.0-2.el6rhs.x86_64 > glusterfs-geo-replication-3.7.0-2.el6rhs.x86_64 > glusterfs-fuse-3.7.0-2.el6rhs.x86_64 > glusterfs-api-3.7.0-2.el6rhs.x86_64 > glusterfs-3.7.0-2.el6rhs.x86_64 > glusterfs-server-3.7.0-2.el6rhs.x86_64 > > > How reproducible: > > 100% > > Steps to Reproduce: > [root@darkknight ~]# gluster v quota vol0 limit-usage / 0 > volume quota : success > [root@darkknight ~]# gluster v quota vol0 list > Path Hard-limit Soft-limit Used > Available Soft-limit exceeded? Hard-limit exceeded? > ----------------------------------------------------------------------------- > ---------------------------------------------- > / 0Bytes 80% 12.0KB > 0Bytes Yes Yes > > [root@darkknight ~]# gluster v quota vol0 limit-usage /test 0MB > volume quota : success > [root@darkknight ~]# gluster v quota vol0 list > Path Hard-limit Soft-limit Used > Available Soft-limit exceeded? Hard-limit exceeded? > ----------------------------------------------------------------------------- > ---------------------------------------------- > / 0Bytes 80% 12.0KB > 0Bytes Yes Yes > /test 0Bytes 80% 0Bytes > 0Bytes Yes Yes > > > Actual results: > > quota limit-usage command accepts zero as valid value > > Expected results: > > quota limit-usage command should not accept zero values > > > Additional info: > > [root@darkknight ~]# gluster v info vol0 > > Volume Name: vol0 > Type: Distributed-Replicate > Volume ID: 4c1a4242-08e0-4cf3-830b-91dd5f78e4b8 > Status: Started > Number of Bricks: 2 x 2 = 4 > Transport-type: tcp > Bricks: > Brick1: 10.70.33.214:/rhs/brick1/b1 > Brick2: 10.70.33.219:/rhs/brick1/b2 > Brick3: 10.70.33.225:/rhs/brick1/b3 > Brick4: 10.70.44.13:/rhs/brick1/b4 > Options Reconfigured: > features.quota-deem-statfs: on > features.inode-quota: on > features.quota: on > features.uss: enable > performance.readdir-ahead: on Hi, In case where the user just wants to create volume and restrict creating files on it(may be a test volume to just check) the user could set quota limit to be 0. As per comment #2, closing bug as 'Not a Bug' |
Description of problem: when you set limit-usage on root or sub-directory, if should not accept zeros values. Version-Release number of selected component (if applicable): [root@darkknight ~]# rpm -qa | grep glusterfs glusterfs-libs-3.7.0-2.el6rhs.x86_64 glusterfs-cli-3.7.0-2.el6rhs.x86_64 glusterfs-client-xlators-3.7.0-2.el6rhs.x86_64 glusterfs-geo-replication-3.7.0-2.el6rhs.x86_64 glusterfs-fuse-3.7.0-2.el6rhs.x86_64 glusterfs-api-3.7.0-2.el6rhs.x86_64 glusterfs-3.7.0-2.el6rhs.x86_64 glusterfs-server-3.7.0-2.el6rhs.x86_64 How reproducible: 100% Steps to Reproduce: [root@darkknight ~]# gluster v quota vol0 limit-usage / 0 volume quota : success [root@darkknight ~]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 0Bytes 80% 12.0KB 0Bytes Yes Yes [root@darkknight ~]# gluster v quota vol0 limit-usage /test 0MB volume quota : success [root@darkknight ~]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 0Bytes 80% 12.0KB 0Bytes Yes Yes /test 0Bytes 80% 0Bytes 0Bytes Yes Yes Actual results: quota limit-usage command accepts zero as valid value Expected results: quota limit-usage command should not accept zero values Additional info: [root@darkknight ~]# gluster v info vol0 Volume Name: vol0 Type: Distributed-Replicate Volume ID: 4c1a4242-08e0-4cf3-830b-91dd5f78e4b8 Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: 10.70.33.214:/rhs/brick1/b1 Brick2: 10.70.33.219:/rhs/brick1/b2 Brick3: 10.70.33.225:/rhs/brick1/b3 Brick4: 10.70.44.13:/rhs/brick1/b4 Options Reconfigured: features.quota-deem-statfs: on features.inode-quota: on features.quota: on features.uss: enable performance.readdir-ahead: on