Red Hat Bugzilla – Bug 1266883
protocol/server: do not define the number of inodes in terms of memory units
Last modified: 2016-06-16 09:39:10 EDT
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):
Steps to Reproduce:
COMMIT: http://review.gluster.org/12242 committed in master by Niels de Vos (email@example.com)
Author: Raghavendra Bhat <firstname.lastname@example.org>
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.
Signed-off-by: Raghavendra Bhat <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Reviewed-by: Niels de Vos <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.