Gluster users - Aug 2015 - Gluster 3.6.4 tune2fs and inode size errors

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

-Atin
Sent from one plus one
On Aug 11, 2015 7:54 PM, "Davy Croonen" <davy.croonen at
smartbit.be> wrote:
>
> 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
I will check this and get back to you.
>
> 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
Have you bump up the op version to 30603? Otherwise glusterd will still
have cluster locking and then multiple commands can't run
simultaneously.
>
> 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?
The error messages are not because of this.
>
> Kind regards
> Davy
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150811/8fb42980/attachment.html>