External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-03 19:45:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Clarify semantics of sparse storage volumes

Browse Source 
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).
This commit is contained in:
Jiri Denemark 2013-03-11 14:42:40 +01:00
parent 1715c83b5f
commit 11677e081b
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/formatstorage.html.in
View File

@ -250,7 +250,11 @@
allocated at time of creation. If set to a value smaller than the allocated at time of creation. If set to a value smaller than the
capacity, the pool has the <strong>option</strong> of deciding capacity, the pool has the <strong>option</strong> of deciding
to sparsely allocate a volume. It does not have to honour requests 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/> <br/>
By default this is specified in bytes, but an optional attribute By default this is specified in bytes, but an optional attribute
<code>unit</code> can be specified to adjust the passed value. <code>unit</code> can be specified to adjust the passed value.