[libvirt] [PATCHv2 6/7] 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. --- docs/formatstorage.html.in | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in index a089a31..1cd82b4 100644 --- a/docs/formatstorage.html.in +++ b/docs/formatstorage.html.in @@ -311,8 +311,10 @@ <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> <dt><code>key</code></dt> - <dd>Providing an identifier for the volume which is globally unique. - This cannot be set when creating a volume: it is always generated. + <dd>Providing an identifier for the volume which identifies a + 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> <dt><code>allocation</code></dt> <dd>Providing the total storage allocation for the volume. This -- 1.9.0