Bug 764390 (GLUSTER-2658) - max_file_size and min_file_size can be set to exceed cache_size
Summary: max_file_size and min_file_size can be set to exceed cache_size
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-2658
Product: GlusterFS
Classification: Community
Component: io-cache
Version: 3.1.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-02 06:47 UTC by Joe Julian
Modified: 2015-11-03 23:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Joe Julian 2011-04-02 06:47:23 UTC 
Unless I'm just missing it, neither file size parameter is checked to see if it exceeds the cache size in io-cache.c:validate_options.
Comment 1 krishnan parthasarathi 2011-04-27 07:36:14 UTC 
max_file_size and min_file_size are bounds on the size of files that the user wants glusterfs to cache. Its a way by which user can selectively turn caching off.
OTOH, cache_size is the amount of memory user sets aside for glusterfs to use for caching files. {min, max}_file_size and cache_size are independent of each other. Closing the bug as invalid.
Note You need to log in before you can comment on or make changes to this bug.