[libvirt] [PATCH] docs: Clarify semantics of sparse storage volumes

[Eric Blake]

On 03/11/2013 07:46 AM, Jiri Denemark wrote:
> Sparse LVM volumes do not behave in the way one would naively expect.
> The allocation does not automatically increase (which is different from
> how sparse files work).
> ---
>  docs/formatstorage.html.in | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)

ACK.

> 
> diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in
> index 9f93db8..8ac7ab1 100644
> --- a/docs/formatstorage.html.in
> +++ b/docs/formatstorage.html.in
> @@ -250,7 +250,11 @@
>          allocated at time of creation. If set to a value smaller than the
>          capacity, the pool has the <strong>option</strong> of deciding
>          to sparsely allocate a volume. It does not have to honour requests
> -        for sparse allocation though.<br/>
> +        for sparse allocation though. Different types of pools may treat
> +        sparse volumes differently. For example, the <code>logical</code>
> +        pool will not automatically expand volume's allocation when it
> +        gets full; the user is responsible for doing that or configuring
> +        dmeventd to do so automatically.<br/>
>          <br/>
>          By default this is specified in bytes, but an optional attribute
>          <code>unit</code> can be specified to adjust the passed value.
> 

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 621 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20130311/fd0640c2/attachment-0001.sig>