This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 837684 - Most commands cause glusterd 3.2.7 to crash on Debian Wheezy
Most commands cause glusterd 3.2.7 to crash on Debian Wheezy
Product: GlusterFS
Classification: Community
Component: cli (Show other bugs)
Unspecified Other
medium Severity medium
: ---
: ---
Assigned To: Kaushal
Depends On:
  Show dependency treegraph
Reported: 2012-07-04 14:28 EDT by Louis Zuckerman
Modified: 2013-07-24 13:30 EDT (History)
5 users (show)

See Also:
Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-24 13:30:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Debian BTS 679767 None None None 2012-07-04 14:28:07 EDT

  None (edit)
Description Louis Zuckerman 2012-07-04 14:28:07 EDT
Description of problem:

Glusterd dies during handling of most gluster CLI commands (vol create, start, stop, delete, at least)

Version-Release number of selected component (if applicable):

Glusterd v. 3.2.7

How reproducible:

Easy to reproduce & consistent.

Steps to Reproduce:
1. Build glusterfs on Debian Sid/Wheezy or install from Debian repository
2. Try to create a volume (gluster volume create foo thishost:/var/tmp/foo0)
3. The volume gets created but glusterd dies in the process
Actual results:

"Connection failed. Please check if gluster daemon is operational."

Starting glusterd up again you can run 'gluster volume info' and see the volume was created.  You can then start the volume, but glusterd will crash once more.  Same for stopping & deleting the volume: glusterd crashes after each operation, but operations appear to have worked after restarting glusterd & running 'gluster volume info' (which does not crash glusterd.)

Expected results:

Normal "volume created" message reminding me to start the volume.

Additional info:

Original bug report in Debian bug tracker:

Crash dump in the glusterd log file from my (successful) attempt to reproduce:

patchset: git://
signal received: 11
time of crash: 2012-07-04 14:11:41
configuration details:
argp 1
backtrace 1
dlfcn 1
fdatasync 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.2.7
Comment 1 Amar Tumballi 2012-07-11 00:59:36 EDT
Looks like an issue with gcc optimization flags. Working on it to get more clarity.

As a work around, giving 'CFLAGS=-O0' fixed the issue.
Comment 2 Patrick Matthäi 2012-07-13 09:56:03 EDT
Thanks but to have glusterfs in our release we have to use the optimizing flags :(
Comment 3 Vijay Bellur 2012-07-20 19:13:19 EDT
CHANGE: (Most commands cause glusterd 3.2.7 to crash on Debian Wheezy) merged in release-3.2 by Anand Avati (
Comment 4 Patrick Matthäi 2012-07-24 03:38:02 EDT
Looks good, Louis and myself tested it.

Patch already uploaded to Debian, thanks!
Comment 5 Kaleb KEITHLEY 2012-08-28 08:27:11 EDT
Despite having tested previously on Fedora 17 (w/ gcc-4.7.0) and found no problem, yesterday while running the 'official' Fedora build of 3.2.7 I ran into the same problem.

glusterfs-3.2.7-2 contains the fix.
Comment 6 Patrick Matthäi 2012-08-28 08:28:37 EDT
3.2.7-2 from Debian also has got the patch and it works :)

Note You need to log in before you can comment on or make changes to this bug.