andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: editing admin setting volumes

Browse Source 
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 <shravantc@ymail.com>
Reviewed-on: http://review.gluster.org/10044
Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
This commit is contained in:
shravantc 2015-03-30 14:59:35 +05:30 committed by Kaleb KEITHLEY
parent 8277b02a94
commit 3fdecc25b4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/admin-guide/en-US/markdown/admin_setting_volumes.md
View File

@ -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.