openkylin
/
libvirt
mirror of https://gitee.com/openkylin/libvirt.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

doc: storage: Explicitly state that it's possible to have non-unique key 

With most of our storage backends it's possible to have two separate
volume keys to point to a single volume. (By creating sym/hard-links to
local files or by mounting remote filesystems to two different locations
and creating pools on top of them) Document this possibility.
This commit is contained in:
Peter Krempa 2014-03-03 16:39:40 +01:00
parent 46446313e8
commit aa50a5c727
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/formatstorage.html.in
View File

@ -311,8 +311,10 @@
<dd>Providing a name for the volume which is unique to the pool. <dd>Providing a name for the volume which is unique to the pool.
This is mandatory when defining a volume. <span class="since">Since 0.4.1</span></dd> This is mandatory when defining a volume. <span class="since">Since 0.4.1</span></dd>
<dt><code>key</code></dt> <dt><code>key</code></dt>
<dd>Providing an identifier for the volume which is globally unique. <dd>Providing an identifier for the volume which identifies a
This cannot be set when creating a volume: it is always generated. single volume. In some cases it's possible to have two distinct keys
identifying a single volume. This field cannot be set when creating
a volume: it is always generated.
<span class="since">Since 0.4.1</span></dd> <span class="since">Since 0.4.1</span></dd>
<dt><code>allocation</code></dt> <dt><code>allocation</code></dt>
<dd>Providing the total storage allocation for the volume. This <dd>Providing the total storage allocation for the volume. This