From 3183f5ad301d86c59f20cb475cc4471730d3d17c Mon Sep 17 00:00:00 2001 From: John Ferlan Date: Mon, 12 Mar 2018 11:26:24 -0400 Subject: [PATCH] virsh: Fix man page argument ordering for vol-delete command The proper command order is 'virsh vol-delete volume pool'. While making the modification clean up the description a bit too in order to help clarify under what circumstances the volume could be found if the pool name was not provided. Signed-off-by: John Ferlan --- tools/virsh.pod | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/tools/virsh.pod b/tools/virsh.pod index c4be774dd5..59c4120409 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -4057,13 +4057,18 @@ When I<--reflink> is specified, perform a COW lightweight copy, where the data blocks are copied only when modified. If this is not possible, the copy fails. -=item B [I<--pool> I] I +=item B I [I<--pool> I] [I<--delete-snapshots>] Delete a given volume. -I<--pool> I is the name or UUID of the storage pool the volume -is in. -I is the name or key or path of the volume to delete. + +I is the volume name or key or path of the volume +to delete. + +[I<--pool> I] is the name or UUID of the storage pool the volume +is in. If the volume name is provided instead of the key or path, then +providing the pool is necessary to find the volume to be deleted; otherwise, +the first volume found by the key or path will be used. The I<--delete-snapshots> flag specifies that any snapshots associated with the storage volume should be deleted as well. Not all storage drivers -- 2.47.2