Bug 831568 - validation of cache-size value
Summary: validation of cache-size value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-13 10:30 UTC by Anush Shetty
Modified: 2013-07-24 17:34 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:34:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Anush Shetty 2012-06-13 10:30:47 UTC 
Description of problem: Currently a user can set the cache-size value to 0 using volume set but mounting the fuse client fails when the cache-size is set to 0


Version-Release number of selected component (if applicable): 3.3.0qa45


How reproducible: Consistently


Steps to Reproduce:
1. gluster volume set amitest performance.cache-size 0
2.
3.
  
Actual results: 

Mounting fuse client fails 


Expected results:

Should we disallow setting the cache-size to 0?

Additional info:
Comment 1 Amar Tumballi 2012-07-11 05:17:18 UTC 
fixed in http://review.gluster.com/3570 in master.
Note You need to log in before you can comment on or make changes to this bug.