Re: [Gluster-users] Bug 1442983 on 3.10.11 Unable to acquire lock for gluster volume leading to 'another transaction in progress' error

2018-03-18 Thread Atin Mukherjee
The fix is already available from glusterfs-3.12.3 onwards. Please refer https://bugzilla.redhat.com/show_bug.cgi?id=1503239 . On Sat, Mar 17, 2018 at 2:21 PM, Paolo Margara wrote: > Hi, > > this patch it's already available in the community version of gluster > 3.12?

Re: [Gluster-users] Bug 1442983 on 3.10.11 Unable to acquire lock for gluster volume leading to 'another transaction in progress' error

2018-03-17 Thread Paolo Margara
Hi, this patch it's already available in the community version of gluster 3.12? In which version? If not, there is plan to backport it? Greetings,     Paolo Il 16/03/2018 13:24, Atin Mukherjee ha scritto: > Have sent a backport request https://review.gluster.org/19730 at > release-3.10

Re: [Gluster-users] Bug 1442983 on 3.10.11 Unable to acquire lock for gluster volume leading to 'another transaction in progress' error

2018-03-16 Thread Marco Lorenzo Crociani
On 16/03/2018 13:24, Atin Mukherjee wrote: Have sent a backport request https://review.gluster.org/19730 at release-3.10 branch. Hopefully this fix will be picked up in next update. Ok thanks! -- Marco Crociani Prisma Telecom Testing S.r.l. ___

Re: [Gluster-users] Bug 1442983 on 3.10.11 Unable to acquire lock for gluster volume leading to 'another transaction in progress' error

2018-03-16 Thread Atin Mukherjee
Have sent a backport request https://review.gluster.org/19730 at release-3.10 branch. Hopefully this fix will be picked up in next update. On Fri, Mar 16, 2018 at 4:47 PM, Marco Lorenzo Crociani < mar...@prismatelecomtesting.com> wrote: > Hi, > I'm hitting bug

[Gluster-users] Bug 1442983 on 3.10.11 Unable to acquire lock for gluster volume leading to 'another transaction in progress' error

2018-03-16 Thread Marco Lorenzo Crociani
Hi, I'm hitting bug https://bugzilla.redhat.com/show_bug.cgi?id=1442983 on glusterfs 3.10.11 and oVirt 4.1.9 (and before on glusterfs 3.8.14) The bug report says fixed in glusterfs-3.12.2-1 Is there a plan to backport the fix to 3.10.x releases or the only way to fix is upgrade to 3.12?