[Gluster-users] Gluster 3.6.4 tune2fs and inode size errors

Davy Croonen
2015-08-11T14:24:42Z

Hi all

Our etc-glusterfs-glusterd.vol.log is filling up with entries as shown:

[2015-08-11 11:40:33.807940] E
[glusterd-utils.c:7410:glusterd_add_inode_size_to_dict] 0-management: tune2fs
exited with non-zero exit status
[2015-08-11 11:40:33.807962] E
[glusterd-utils.c:7436:glusterd_add_inode_size_to_dict] 0-management: failed to
get inode size

From the mailinglist archive I could understand this was a problem in gluster
version 3.4 and should be fixed. We started out from version 3.5 and upgraded in
the meantime to version 3.6.4 but the error in the errorlog still exists.

We are also unable to execute the command

$gluster volume status all inode

as a result gluster hangs up with the message: ?Another transaction is in
progress. Please try again after sometime.? while executing the command

$gluster volume status

Are the error messages in the logs related to the hung up of gluster while
executing the mentioned commands? And any ideas about how to fix this?

Kind regards
Davy