<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Aug 11, 2015 7:54 PM, "Davy Croonen" <<a href="mailto:davy.croonen@smartbit.be">davy.croonen@smartbit.be</a>> wrote:<br>
><br>
> Hi all<br>
><br>
> Our etc-glusterfs-glusterd.vol.log is filling up with entries as shown:<br>
><br>
> [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<br>
> [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<br>
I will check this and get back to you.<br>
><br>
> 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.<br>
><br>
> We are also unable to execute the command<br>
><br>
> $gluster volume status all inode<br>
><br>
> as a result gluster hangs up with the message: “Another transaction is in progress. Please try again after sometime.” while executing the command<br>
><br>
> $gluster volume status<br>
Have you bump up the op version to 30603? Otherwise glusterd will still have cluster locking and then multiple commands can't run simultaneously.<br>
><br>
> 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?<br>
The error messages are not because of this.<br>
><br>
> Kind regards<br>
> Davy<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></p>