diff options
| author | Susant Palai <spalai@redhat.com> | 2018-02-26 11:33:06 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2018-05-03 17:57:33 +0000 |
| commit | c63b278947dbc134e08331a097cf2041cf98c545 (patch) | |
| tree | a21b05bdc4ed7c27abfeaa61b25d949e0acf07bd /cli/src/cli.h | |
| parent | f46047ea0f36084f4456887673552a01b926382d (diff) | |
cli/glusterd: Add warning message in cli for user to check
force-migration config for remove-brick operation.
The cli will take input from the user before starting "remove-brick"
start operation. The message/confirmation looks like the following:
<Running remove-brick with cluster.force-migration enabled can result
in data corruption. It is safer to disable this option so that files
that receive writes during migration are not migrated. Files that are
not migrated can then be manually copied after the remove-brick commit
operation. Do you want to continue with your current
cluster.force-migration settings? (y/n)>
And also question for COMMIT_FORCE is changed.
Fixes: bz#1572586
Change-Id: Ifdb6b108a646f50339dd196d6e65962864635139
Signed-off-by: Susant Palai <spalai@redhat.com>
Diffstat (limited to 'cli/src/cli.h')
| -rw-r--r-- | cli/src/cli.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cli/src/cli.h b/cli/src/cli.h index 68dcb8c531f..3421d6911fb 100644 --- a/cli/src/cli.h +++ b/cli/src/cli.h @@ -279,7 +279,7 @@ cli_cmd_volume_old_tier_parse (const char **words, int wordcount, int32_t cli_cmd_volume_remove_brick_parse (const char **words, int wordcount, dict_t **options, int *question, - int *brick_count); + int *brick_count, int32_t *command); int32_t cli_cmd_volume_replace_brick_parse (const char **words, int wordcount, |