The proper command order is 'virsh vol-info 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 <jferlan@xxxxxxxxxx> --- tools/virsh.pod | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/tools/virsh.pod b/tools/virsh.pod index 135cce841..cd1ccc6fa 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -4190,17 +4190,26 @@ 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 uploaded into; otherwise, the first volume found by the key or path will be used. -=item B<vol-info> [I<--pool> I<pool-or-uuid>] I<vol-name-or-key-or-path> +=item B<vol-info> I<vol-name-or-key-or-path> [I<--pool> I<pool-or-uuid>] [I<--bytes>] [I<--physical>] Returns basic information about the given storage volume. + +I<vol-name-or-key-or-path> is the name or key or path of the volume +to return information for. + I<--pool> I<pool-or-uuid> is the name or UUID of the storage pool the volume -is in. I<vol-name-or-key-or-path> is the name or key or path of the volume -to return information for. If I<--bytes> is specified the sizes are not -converted to human friendly units. If I<--physical> is specified, then the host -physical size is returned and displayed instead of the allocation value. The -physical value for some file types, such as qcow2 may have a different (larger) -physical value than is shown for allocation. Additionally sparse files will +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 uploaded into; +otherwise, the first volume found by the key or path will be used. + +If I<--bytes> is specified the sizes are not converted to human friendly +units. + +If I<--physical> is specified, then the host physical size is returned +and displayed instead of the allocation value. The physical value for +some file types, such as qcow2 may have a different (larger) physical +value than is shown for allocation. Additionally sparse files will have different physical and allocation values. =item B<vol-list> [I<--pool> I<pool-or-uuid>] [I<--details>] -- 2.13.6 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
