Description of problem: Replace-brick has not been started. Any operation done using replace-brick does not report that replace-brick has been started. root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 Usage: volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> {start|pause|abort|status|commit [force]} root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 commit replace-brick commit failed root@Dagobah:~# gluster volume info backup Volume Name: backup Type: Distribute Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: dagobah:/tmp/brick Brick2: dagobah:/tmp/brick1 root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 abort replace-brick abort failed root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 pause replace-brick pause failed root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 commit force incorrect source or destination brick (This error message does not make sense as to why commit force has failed.) root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 start replace-brick started successfully Only root@Dagobah:~# gluster volume replace-brick backup dagobah:/tmp/brick dagobah:/tmp/brick2 status shows proper message saying that replace-brick is not started.
planning to remove replace-brick... (http://review.gluster.org/6031) and hence marking the bug as WONTFIX