Bug 804526 - quota timeout is 0 even though the valid range is 1-60
Summary: quota timeout is 0 even though the valid range is 1-60
Keywords:
Status: CLOSED DUPLICATE of bug 804509
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 07:30 UTC by Anush Shetty
Modified: 2012-03-19 09:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-19 09:40:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Anush Shetty 2012-03-19 07:30:27 UTC
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}}
};

Comment 1 Kaushal 2012-03-19 09:40:28 UTC

*** This bug has been marked as a duplicate of bug 804509 ***


Note You need to log in before you can comment on or make changes to this bug.