[pve-devel] [PATCH docs] pvesm: improve file level based storage paragraph

Thomas Lamprecht t.lamprecht at proxmox.com
Tue Dec 11 13:05:02 CET 2018


improve the file level based storage paragraph bit and move it above
the block based one, as the table is sorted by storage type, and file
comes first.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---

Adaption of order matchin between table and above paragraphs where requested by
Daniela, makes more sense from a lingustic point ovf view.

 pvesm.adoc | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/pvesm.adoc b/pvesm.adoc
index 6776385..cbe496e 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -48,6 +48,13 @@ Storage Types
 
 There are basically two different classes of storage types:
 
+File level storage::
+
+File level based storage technologies allow access to a full featured (POSIX)
+file system.  They are in general more flexible than any Block level storage
+(see below), and allow you to store content of any type. ZFS is probably the
+most advanced system, and it has full support for snapshots and clones.
+
 Block level storage::
 
 Allows to store large 'raw' images. It is usually not possible to store
@@ -56,13 +63,6 @@ block level storage implementations support snapshots and clones.
 RADOS, Sheepdog and GlusterFS are distributed systems, replicating storage
 data to different nodes.
 
-File level storage::
-
-They allow access to a full featured (POSIX) file system. They are
-more flexible, and allows you to store any content type. ZFS is
-probably the most advanced system, and it has full support for
-snapshots and clones.
-
 
 .Available storage types
 [width="100%",cols="<d,1*m,4*d",options="header"]
-- 
2.19.2





More information about the pve-devel mailing list