Description of problem: The maximum number of inodes in the inode table is being defined as memory units instead of number. So is the description of the option. .max = (1 * GF_UNIT_MB), .description = "Specifies the maximum megabytes of memory to be " "used in the inode cache. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
COMMIT: http://review.gluster.org/12242 committed in master by Niels de Vos (ndevos) ------ commit 0c02fefaf7d6b54f4d9cae2b1ae1f2b657857625 Author: Raghavendra Bhat <raghavendra> Date: Mon Sep 28 16:47:01 2015 +0530 protocol/server: define the max number of inodes in lru list as a number * The max number of inodes in the lru list of the inode table was being defined in terms of memory units (GF_UNIT_MB) instead of number. And the description of the option was also referring to it in memory units instead of number. Change-Id: I48f07e7d2826406697eb2a13714ab22feae81d89 BUG: 1266883 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/12242 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user