summaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING
diff options
context:
space:
mode:
authorAtin Mukherjee <amukherj@redhat.com>2014-03-19 11:30:22 +0530
committerVijay Bellur <vbellur@redhat.com>2014-04-02 12:04:11 -0700
commit5dedef81b6ef91d462ce49ded4e148dfc17deee2 (patch)
treeccbc094f6fe53d55780dadda5dd35e535a3bdb66 /CONTRIBUTING
parente75be8977ede9b9174d20b39c427e6fb4ccde567 (diff)
cli: remove-brick no longer defaults to commit-force
Problem : When gluster volume remove-brick is executed with out any option, it defaults to force commit which results in data loss. Fix : remove-brick can not be executed with out explicit option, user needs to provide the option in the command line else the command will throw back an usage error. Earlier usage : volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ... [start|stop|status|commit|force] Current usage : volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ... <start|stop|status|commit|force> Change-Id: I2a49131f782a6c0dcd03b4dc8ebe5907999b0b49 BUG: 1077682 Signed-off-by: Atin Mukherjee <amukherj@redhat.com> Reviewed-on: http://review.gluster.org/7292 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Shyamsundar Ranganathan <sam.somari@gmail.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'CONTRIBUTING')
0 files changed, 0 insertions, 0 deletions