Description of problem: Version-Release number of selected component (if applicable): mainline How reproducible: always Steps to Reproduce: Steps are pretty basic. crash can be observed by just invoking gsyncd binary Actual results: gsyncd binary crashes. Expected results: No crashes. Should work as expected.
REVIEW: http://review.gluster.org/7683 (gsyncd / geo-rep: Initialize default memory accounting) posted (#1) for review on master by Venky Shankar (vshankar)
COMMIT: http://review.gluster.org/7683 committed in master by Venky Shankar (vshankar) ------ commit b8cd471dbaadfa6ff9a92789f8fd670c144f9e9e Author: Venky Shankar <vshankar> Date: Tue May 6 16:04:43 2014 +0530 gsyncd / geo-rep: Initialize default memory accounting commit 7fba3a8 enables memory accounting by default. Since geo-replication binary (gsyncd) does not declare a memory accounting function, call like GF_{CALLOC,MALLOC} result int asserts. This patch initializes default memory accounting. Change-Id: I9ad1de8bca6745a9899a006a863a7cfeef73d52f BUG: 1094708 Signed-off-by: Venky Shankar <vshankar> Reviewed-on: http://review.gluster.org/7683 Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/7698 (libgfchangelog: memory accouting intialization) posted (#1) for review on master by Venky Shankar (vshankar)
Patch for libgfachangelog experiencing similar backtraces: http://review.gluster.org/#/c/7698/
REVIEW: http://review.gluster.org/7698 (libgfchangelog: memory accounting intialization) posted (#2) for review on master by Venky Shankar (vshankar)
COMMIT: http://review.gluster.org/7698 committed in master by Venky Shankar (vshankar) ------ commit 933f60796d69686a153659c7b178dbd1475f9cb6 Author: Venky Shankar <vshankar> Date: Wed May 7 18:03:34 2014 +0530 libgfchangelog: memory accounting intialization Needed as memory accounting turned ON by default now. Without this, GF_{CALLOC,MALLOC} calls assert. Change-Id: Ie54a6efb61871e70d4f7c796d9c86a867051e2e0 BUG: 1094708 Signed-off-by: Venky Shankar <vshankar> Reviewed-on: http://review.gluster.org/7698 Reviewed-by: Kotresh HR <khiremat>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users