Description of problem: smbd process terminates with SIGABRT, when a remote client attempts to mount glusterfs share. Note that this happens when glusterfs is built with -DDEBUG flag. Version-Release number of selected component (if applicable): How reproducible: Often Steps to Reproduce: 1. Create and start a volume. 2. Start smbd service 3. Mount the share from a remote client. Mount fails. Actual results: On inspecting the samba logs and the core files location, it was found that smbd process had crashed with SIGABRT. Expected results: Mount must not fail, and smbd must not crash. Additional info:
REVIEW: http://review.gluster.org/6134 (gfapi: fix mem-types initialisation) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/6134 committed in master by Anand Avati (avati) ------ commit 93c49c6e8c443426792b8e6cf24805516fdcc9bd Author: Krutika Dhananjay <kdhananj> Date: Wed Oct 23 13:39:18 2013 +0000 gfapi: fix mem-types initialisation ... and also fill the body of mem_acct_init(). Change-Id: I457d0629c20f999dd2f50e710c75b1c7575b6c19 BUG: 1021904 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/6134 Reviewed-by: Amar Tumballi <amarts> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
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.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user