Hi Atin
Any news on this one?
KR
Davy
On 12 Aug 2015, at 16:41, Atin Mukherjee
atin.mukherje...@gmail.commailto:atin.mukherje...@gmail.com wrote:
Davy,
I will check this with Kaleb and get back to you.
-Atin
Sent from one plus one
On Aug 12, 2015 7:22 PM, Davy Croonen
I've not got a chance to look at it which I will do now. Thanks for
reminder!
-Atin
Sent from one plus one
On Aug 17, 2015 7:19 PM, Davy Croonen davy.croo...@smartbit.be wrote:
Hi Atin
Any news on this one?
KR
Davy
On 12 Aug 2015, at 16:41, Atin Mukherjee atin.mukherje...@gmail.com
On 08/18/2015 10:41 AM, Atin Mukherjee wrote:
Just a quick update. I was wrong saying the issue is reproducible in
3.7. What I could see is this issue is fixed in 3.7. Now I need to find
out the patch which fixed it and backport it to 3.6. Would it be
possible for you to upgrade the setup to
Just a quick update. I was wrong saying the issue is reproducible in
3.7. What I could see is this issue is fixed in 3.7. Now I need to find
out the patch which fixed it and backport it to 3.6. Would it be
possible for you to upgrade the setup to 3.7 if you want a quick solution?
~Atin
On
Davy,
I will check this with Kaleb and get back to you.
-Atin
Sent from one plus one
On Aug 12, 2015 7:22 PM, Davy Croonen davy.croo...@smartbit.be wrote:
Atin
No problem to raise a bug for this, but isn’t this already addressed here:
Bug 670
Hi Atin
Thanks for your answer. The op-version was indeed an old one, 30501 to be
precise. I’ve updated the op-version to the one you suggested with the command:
gluster volume set all cluster.op-version 30603. From testing it seems this
issue is solved for the moment.
Considering the errors
Well, this looks like a bug even in 3.7 as well. I've posted a fix [1]
to address it.
[1] http://review.gluster.org/11898
Could you please raise a bug for this?
~Atin
On 08/12/2015 01:32 PM, Davy Croonen wrote:
Hi Atin
Thanks for your answer. The op-version was indeed an old one, 30501 to
Atin
No problem to raise a bug for this, but isn’t this already addressed here:
Bug 670https://bugzilla.redhat.com/show_bug.cgi?id=670 - continuous
log entries failed to get inode size
https://bugzilla.redhat.com/show_bug.cgi?id=670#c2
KR
Davy
On 12 Aug 2015, at 14:56, Atin
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
-Atin
Sent from one plus one
On Aug 11, 2015 7:54 PM, Davy Croonen davy.croo...@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
10 matches
Mail list logo
