Description of problem: It seems that the inode size of a brick is never set correctly. The command # gluster volume status $PATH_TO_BRICK detail always fails and sets the "inode size" to N/A. Version-Release number of selected component (if applicable): any? How reproducible: 100% Steps to Reproduce: 1. gluster volume status $PATH_TO_BRICK detail Actual results: Status of volume: bug-1081016 ------------------------------------------------------------------------------ Brick : Brick vm130-111.example.com:/bricks/bug-1081016/data Port : 49152 Online : Y Pid : 24647 File System : xfs Device : /dev/mapper/vg_bricks-bug--1081016 Mount Options : rw Inode Size : N/A Disk Space Free : 481.5MB Total Disk Space : 507.3MB Inode Count : 524288 Free Inodes : 524275 Expected results: Status of volume: bug-1081016 ------------------------------------------------------------------------------ Brick : Brick vm130-111.example.com:/bricks/bug-1081016/data Port : 49152 Online : Y Pid : 24647 File System : xfs Device : /dev/mapper/vg_bricks-bug--1081016 Mount Options : rw Inode Size : 256 Disk Space Free : 481.5MB Total Disk Space : 507.3MB Inode Count : 524288 Free Inodes : 524275 Additional info:
REVIEW: http://review.gluster.org/8492 (glusterd: really get the inode size for a brick) posted (#1) for review on master by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/8492 committed in master by Krishnan Parthasarathi (kparthas) ------ commit b2ae71dbcf1b932abc16f096eee74d50aa823b04 Author: Niels de Vos <ndevos> Date: Fri Aug 15 11:13:46 2014 +0200 glusterd: really get the inode size for a brick The device to get the inode size from does not get passed to the tool (tune2fs, xfs_info or the like) that is called. This is probably just an oversight. While correcting this, cleanup some bits of the function too. Change-Id: Ida45852cba061631fb304bc7dd5286df1a808010 BUG: 1130462 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/8492 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user