NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2026-09-03 20:53:04 -05:00
Code Issues Packages Projects Releases Wiki Activity

Fix documentation cut and paste errors, and a virsh typo.

Browse Source
This commit is contained in:
Cole Robinson
2008-12-04 14:51:57 +00:00
parent b9b9c8b020
commit 76944e8137
4 changed files with 13 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/formatstorage.html.in
+4 -11
View File
@@ -245,17 +245,10 @@
<dl>
<dt><code>path</code></dt>
<dd>Provides the location at which the pool will be mapped into
the local filesystem namespace. For a filesystem/directory based
pool it will be the name of the directory in which volumes will
be created. For device based pools it will be the name of the directory in which
devices nodes exist. For the latter <code>/dev/</code> may seem
like the logical choice, however, devices nodes there are not
guaranteed stable across reboots, since they are allocated on
demand. It is preferable to use a stable location such as one
of the <code>/dev/disk/by-{path,id,uuid,label</code> locations.
<span class="since">Since 0.4.1</span>
</dd>
<dd>Provides the location at which the volume can be accessed on
the local filesystem, as an absolute path. This is a readonly
attribute, so shouldn't be specified when creating a volume.
<span class="since">Since 0.4.1</span></dd>
<dt><code>format</code></dt>
<dd>Provides information about the pool specific volume format.
For disk pools it will provide the partition type. For filesystem
docs/storage.html.in
+2 -2
View File
@@ -343,12 +343,12 @@ libvirt.
<h3>Valid pool format types</h3>
<p>
The logical volume pool does not use the pool format type element.
The iSCSI volume pool does not use the pool format type element.
</p>
<h3>Valid volume format types</h3>
<p>
The logical volume pool does not use the volume format type element.
The iSCSI volume pool does not use the volume format type element.
</p>
</body>
</html>