From 7ed89d7421f8a1af619ffa09644eb8837ac71212 Mon Sep 17 00:00:00 2001 From: John Ferlan Date: Sat, 3 Dec 2016 07:53:15 -0500 Subject: [PATCH] docs: Update formatstorage to match code for pool path Seems commit id '0257d06b' forgot to include formatstorage when updating the docs to describe allowing zfs as a pool type and to furthermore note that the pool's target path element will be generated rather than read. Similarly commit id 'efab27afb' neglected to indicate that the target path for a logical pool will now be generated by libvirt. Signed-off-by: John Ferlan --- 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 f1be511dcd..47c8b0c8a7 100644 --- a/docs/formatstorage.html.in +++ b/docs/formatstorage.html.in @@ -380,8 +380,8 @@ pool element for some types of pools (pool types dir, fs, netfs, logical, disk, iscsi, - scsi, mpath). This tag is used to - describe the mapping of + scsi, mpath, zfs). + This tag is used to describe the mapping of the storage pool into the host filesystem. It can contain the following child elements:

@@ -411,6 +411,8 @@ guaranteed stable across reboots, since they are allocated on demand. It is preferable to use a stable location such as one of the /dev/disk/by-{path|id|uuid|label} locations. + For logical and zfs pool types, a + provided value is ignored and a default path generated. For a Multipath pool (type mpath), the provided value is ignored and the default value of "/dev/mapper" is used. Since 0.4.1 -- GitLab