[Bugs] [Bug 1259511] New: Rebalance crashes

bugzilla at redhat.com bugzilla at redhat.com
Wed Sep 2 20:26:30 UTC 2015


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

            Bug ID: 1259511
           Summary: Rebalance crashes
           Product: GlusterFS
           Version: 3.7.3
         Component: unclassified
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: vitaliy at kievinfo.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Created attachment 1069585
  --> https://bugzilla.redhat.com/attachment.cgi?id=1069585&action=edit
Log of the crash

Description of problem:
Attempting to remove 2 bricks from the 2x2 setup was resulting in the crash.
Now with two bricks back, I've added them back in to the cluster. And
attempting to do a rebalance:
# gluster rebalance gv1 start

On all bricks that are part of the cluster rebalance crashes:


Version-Release number of selected component (if applicable):
3.7.3 RPS from gluster.org for OpenSuSE 13.2

How reproducible:
Create 2x2 volume with 4 bricks. Copy some files. Attempt to remove 2 bricks:
# gluster volume remove-brick gv1 brick1:/export brick2:/export

Create volume with 2 replicas. Copy some files. Add 2 more bricks. Attempt to
rebalance:
# gluster volume rebalance gv1 start


Actual results:
# gluster volume rebalance gv1 start
volume rebalance: gv1: success: Rebalance on gv1 has been started successfully.
Use rebalance status command to check status of the rebalance process.
ID: 1dde3a6f-a5f2-41d0-ac49-03b4dd4ac1c6

# gluster volume status
...
Task Status of Volume gv1
------------------------------------------------------------------------------
Task                 : Rebalance
ID                   : 1dde3a6f-a5f2-41d0-ac49-03b4dd4ac1c6
Status               : failed


Expected results:
Rebalance succeeding.

Additional info:
Have core files if you want them.

Core was generated by `/usr/sbin/glusterfs -s localhost --volfile-id
rebalance/gv1 --xlator-option *dh'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x00007f5426d6312b in ?? ()

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list