[Bugs] [Bug 1254421] New: glusterd fails to get the inode size for a brick

bugzilla at redhat.com bugzilla at redhat.com
Tue Aug 18 05:29:57 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1254421

            Bug ID: 1254421
           Summary: glusterd fails to get the inode size for a brick
           Product: GlusterFS
           Version: 3.6.4
         Component: glusterd
          Keywords: Triaged
          Severity: low
          Priority: low
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    ndevos at redhat.com
        Depends On: 1130462



+++ This bug was initially created as a clone of Bug #1130462 +++

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:

--- Additional comment from Anand Avati on 2014-08-15 06:14:33 EDT ---

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 at redhat.com)

--- Additional comment from Anand Avati on 2014-10-28 01:48:32 EDT ---

COMMIT: http://review.gluster.org/8492 committed in master by Krishnan
Parthasarathi (kparthas at redhat.com) 
------
commit b2ae71dbcf1b932abc16f096eee74d50aa823b04
Author: Niels de Vos <ndevos at redhat.com>
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 at redhat.com>
    Reviewed-on: http://review.gluster.org/8492
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle at redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas at redhat.com>

--- Additional comment from Niels de Vos on 2015-05-14 13:27:09 EDT ---

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

--- Additional comment from Niels de Vos on 2015-05-14 13:35:32 EDT ---

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

--- Additional comment from Niels de Vos on 2015-05-14 13:37:54 EDT ---

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

--- Additional comment from Niels de Vos on 2015-05-14 13:43:18 EDT ---

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


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1130462
[Bug 1130462] glusterd fails to get the inode size for a brick
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list