*** Bug 2976 has been marked as a duplicate of this bug. ***
I did the following operation root@tortuga:/tmp# gluster volume set hosdu performance.cache-min-file-size 5MB Set volume successful root@tortuga:/tmp# gluster volume set hosdu performance.cache-max-file-size 1MB Set volume successful min-file-size for caching exceeds max-file-size for caching. There should be a validation to verify it. root@tortuga:/tmp# gluster volume info Volume Name: hosdu Type: Distribute Status: Started Number of Bricks: 3 Transport-type: tcp Bricks: Brick1: tortuga:/tmp/brick1 Brick2: tortuga:/tmp/brick2 Brick3: tortuga:/tmp/brick3 Options Reconfigured: performance.cache-max-file-size: 1MB performance.cache-min-file-size: 5MB
PATCH: http://patches.gluster.com/patch/7362 in master (performance/io-cache: fix the check of min and max file size.)
PATCH: http://patches.gluster.com/patch/7364 in release-3.1 (performance/io-cache: fix the check of min and max file size.)
PATCH: http://patches.gluster.com/patch/7363 in release-3.2 (performance/io-cache: fix the check of min and max file size.)
The patches committed fixes the bug 764708. But this bug will remain open.
The issue still persists in 3.2.1qa4... Is this supposed to be fixed in 3.2.1?
Bug fix happened is for bug 764708, please verify that.
Currently known issue. We don't do the check during the 'volume set' but the check happens when the process is started (volume start/mounting). I guess, best way to fix it is by fixing bug 762935, so the proper error code can be sent to the user too. Currently, lets just document this behavior, so that user is aware of such behavior.
Resolved in http://review.gluster.org/4541. *** This bug has been marked as a duplicate of bug 782095 ***