[Bugs] [Bug 1679892] assertion failure log in glusterd.log file when a volume start is triggered

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1679892

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
             Blocks|                            |1672818 (glusterfs-6.0)



--- Comment #2 from Sanju <srakonde at redhat.com> ---
I still see the assertion failure message in the glusterd.log

[2019-03-12 05:19:06.206695] E [mem-pool.c:351:__gf_free]
(-->/usr/local/lib/glusterfs/6.0rc0/xlator/mgmt/glusterd.so(+0x48133)
[0x7f264602c133]
-->/usr/local/lib/glusterfs/6.0rc0/xlator/mgmt/glusterd.so(+0x47f0a)
[0x7f264602bf0a] -->/usr/local/lib/libglusterfs.so.0(__gf_free+0x22d)
[0x7f265263ac9d] ) 0-: Assertion failed: mem_acct->rec[header->type].size >=
header->size

I will update the bug with root cause as soon as possible.

Thanks,
Sanju


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1672818
[Bug 1672818] GlusterFS 6.0 tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.