From 6801fc385d69a43d829b504adea299cce6057e25 Mon Sep 17 00:00:00 2001 From: "M. Mohan Kumar" Date: Tue, 4 Dec 2012 14:25:33 +0530 Subject: man page update for BD backend xlator BUG: 805138 Change-Id: Ifbceb329ba9039e6617d377c6b7fdb67d2383ddd Signed-off-by: M. Mohan Kumar Reviewed-on: http://review.gluster.org/4274 Reviewed-by: Anand Avati Tested-by: Anand Avati --- doc/gluster.8 | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/gluster.8 b/doc/gluster.8 index 3c78fb8b..b23e2c89 100644 --- a/doc/gluster.8 +++ b/doc/gluster.8 @@ -8,7 +8,7 @@ .\" cases as published by the Free Software Foundation. .\" .\" -.TH Gluster 8 "Gluster command line utility" "07 March 2011" "Gluster Inc." +.TH Gluster 8 "Gluster command line utility" "22 November 2012" "Gluster Inc." .SH NAME gluster - Gluster Console Manager (command line utility) .SH SYNOPSIS @@ -36,9 +36,11 @@ The Gluster Console Manager is a command line utility for elastic volume managem \fB\ volume info [all|] \fR Display information about all volumes, or the specified volume. .TP -\fB\ volume create [stripe ] [replica ] [transport ] ... \fR +\fB\ volume create [device vg] [stripe ] [replica ] [transport ] ... \fR Create a new volume of the specified type using the specified bricks and transport type (the default transport type is tcp). To create a volume with both transports (tcp and rdma), give 'transport tcp,rdma' as an option. +device vg parameter specifies volume should use block backend instead of regular posix backend. In this case NEW-BRICK should specify an existing Volume Group and there can be only one brick for Block backend volumes. \fR +Refer Block backend section for more details .TP \fB\ volume delete \fR Delete the specified volume. @@ -57,6 +59,9 @@ Set the volume options. .TP \fB\ volume help \fR Display help for the volume command. +.SS "Block backend" +.TP +By specifying "device vg" in volume create, a volume capable of exporting block devices(ie Volume Groups (VG)) is created. As of now exporting only VG is supported. While creating block backend volume the "VG" (mentioned in NEW-BRICK) must exist (ie created with vgcreate). VG is exported as a directory and all LVs under that VG will be exported as files. Please refer BD commands section for Block backend related commands .SS "Brick Commands" .PP .TP @@ -105,6 +110,20 @@ Display the status of peers. .TP \fB\ peer help \fR Display help for the peer command. +.SS "BD commands" +.TP +\fB\ bd create \fR +Creates a new image of given size in the volume. Size can be suffixed with MB, GB etc, if nothing specified MB is taken as default. +.TP +\fB\ bd delete \fR +Deletes a image in the volume +.TP +\fB\ bd clone \fR +Clones an existing image (full clone) +.TP +\fB\ bd snapshot \fR +Creates a linked clone of an existing image with given size. Size can be suffixed with MB, GB etc, if nothing specified MB is taken as default. + .SS "Other Commands" .TP \fB\ help \fR -- cgit