|author||shravantc <firstname.lastname@example.org>||2015-03-30 14:59:35 +0530|
|committer||Kaleb KEITHLEY <email@example.com>||2015-03-30 09:45:51 -0700|
doc: editing admin setting volumes
added procedure/steps to format and mount volumes before volumes are created. Includes step by step creation of thinly provisioned volumes. Change-Id: I92325d84d8b322948a7a58daf0de79e2097d252a BUG: 1206539 Signed-off-by: shravantc <firstname.lastname@example.org> Reviewed-on: http://review.gluster.org/10044 Reviewed-by: Lalatendu Mohanty <email@example.com> Tested-by: Gluster Build System <firstname.lastname@example.org>
Diffstat (limited to 'doc/admin-guide/en-US')
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/admin-guide/en-US/markdown/admin_setting_volumes.md b/doc/admin-guide/en-US/markdown/admin_setting_volumes.md
index f4eebcd50fb..a500a7214da 100644
@@ -398,7 +398,7 @@ of this volume type is supported only for Map Reduce workloads.
> - GlusterFS will fail to create a distribute replicate volume if more than one brick of a replica set is present on the same peer. For eg. four node distribute (replicated) volume with a more than one brick of replica set is present on the same peer.
# gluster volume create <volname> stripe 2 replica 2 server1:/brick1 server1:/brick2 server2:/brick3 server4:/brick4
- volume create: <volname>: failed: Multiple bricks of a replicate volume are present on the same server. This setup is not optimal. Use 'force' at the end of the command if you want to override this behavior.```
+ volume create: <volname>: failed: Multiple bricks of a replicate volume are present on the same server. This setup is not optimal. Use `force` at the end of the command if you want to override this behavior.```
> Use the `force` option at the end of command if you want to create the volume in this case.