Created attachment 592323 [details] abrt traceback Description of problem: gluster segfaults Version-Release number of selected component (if applicable): glusterfs-3.2.6-2.fc17.x86_64 How reproducible: Always. Steps to Reproduce: yum -y install wget fuse fuse-libs glusterfs glusterfs-fuse glusterfs-server systemctl enable glusterd.service systemctl start glusterd.service mkdir /mnt/brick{1..4} mkdir /mnt/cluster gluster volume create mediacluster replica 2 transport tcp \ host43.byington.org:/mnt/brick1 \ host43.byington.org:/mnt/brick2 gluster volume start mediacluster Actual results: Connection failed. Please check if gluster daemon is operational. Expected results: volume should start and be available Additional info: ############# #systemctl restart glusterd.service #gluster volume info all Volume Name: mediacluster Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: host43.byington.org:/mnt/brick1 Brick2: host43.byington.org:/mnt/brick2 gluster volume stop mediacluster Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y Connection failed. Please check if gluster daemon is operational. ########### #systemctl restart glusterd.service #gluster volume info all Volume Name: mediacluster Type: Replicate Status: Stopped Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: host43.byington.org:/mnt/brick1 Brick2: host43.byington.org:/mnt/brick2 Attempts to start or stop the volume cause glusterd to segfault. Restarting the service shows the volume has been started or stopped, but it won't mount - same segfault.
The glusterd.service is running on host43.byington.org, talking to two bricks on the same machine: Brick1: host43.byington.org:/mnt/brick1 Brick2: host43.byington.org:/mnt/brick2
I am seeing this as well.
Correction - the volume will mount. Workaround: gluster volume create mediacluster replica 2 transport tcp \ host43.byington.org:/mnt/brick1 \ host43.byington.org:/mnt/brick2 gluster volume start mediacluster --- dies but just restart it. systemctl restart glusterd.service gluster volume info all; # that works mount /mnt/cluster ... ; # and it mounts after a glusterd restart Essentially, volume operations (start, stop, sync) all segfault glusterd, but a simple restart of glusterd.service works, and the volume operation has actually completed; and at that point a mount will work.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
old, seems to not be a problem in later versions.