]> git.ipfire.org Git - thirdparty/libvirt.git/commit
projects / thirdparty / libvirt.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4644631) | patch
doc: storage: Explicitly state that it's possible to have non-unique key
authorPeter Krempa <pkrempa@redhat.com>
Mon, 3 Mar 2014 15:39:40 +0000 (16:39 +0100)
committerPeter Krempa <pkrempa@redhat.com>
Wed, 5 Mar 2014 08:51:24 +0000 (09:51 +0100)
commitaa50a5c727c8c9b65f56854cf91fb8e05f8b68e5
tree9bd94c8ad7ba9b4b642d429f33e878e4cfb318a3tree
parent46446313e8d8021849081bca097ab9195a604bb8commit | diff
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 diff | blob | blame | history
Mirror of https://github.com/libvirt/libvirt.git