Bug 804526
| Summary: | quota timeout is 0 even though the valid range is 1-60 | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Anush Shetty <ashetty> |
| Component: | quota | Assignee: | Raghavendra G <rgowdapp> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | gluster-bugs, kaushal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-19 09:40:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 804509 *** |
Description of problem: When the quota is enabled, the timeout value set is 0 even though the allowed range is from 1-60. All subsequent volume set commands fail due to this. Version-Release number of selected component (if applicable): 3.3.0qa29 How reproducible: Consistently Steps to Reproduce: 1. Create a volume and enable quota 2. 3. Actual results: volume test2-quota type features/quota option timeout 0 subvolumes test2-client-0 end-volume Expected results: Default timeout value should be set to 1 Additional info: In xlators/features/quota/src/quota.c struct volume_options options[] = { {.key = {"limit-set"}}, {.key = {"timeout"}, .type = GF_OPTION_TYPE_SIZET, .min = 1, .max = 60, .default_value = "0", .description = "quota caches the directory sizes on client. Timeout " "indicates the timeout for the cache to be revalidated." }, {.key = {NULL}} };