X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=pve-storage-glusterfs.adoc;h=af4b8577238891491b1d0ef215e5e410d83a0c4e;hb=2409e808814155b485d3f9000fc56f18e83f5862;hp=238450a0ab75151a6ae2365e397ebec6abebec93;hpb=fc3425bdf7c0fca3a2c25c9221a4a3abc3f6d295;p=pve-docs.git diff --git a/pve-storage-glusterfs.adoc b/pve-storage-glusterfs.adoc index 238450a..af4b857 100644 --- a/pve-storage-glusterfs.adoc +++ b/pve-storage-glusterfs.adoc @@ -1,15 +1,18 @@ GlusterFS Backend ----------------- -include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +:title: Storage: GlusterFS +endif::wiki[] Storage pool type: `glusterfs` -GlusterFS is a salable network file system. The system uses a modular +GlusterFS is a scalable network file system. The system uses a modular design, runs on commodity hardware, and can provide a highly available enterprise storage at low costs. Such system is capable of scaling to several petabytes, and can handle thousands of clients. -NOTE: After a node/brick crash, GlusterFS does a full 'rsync' to make +NOTE: After a node/brick crash, GlusterFS does a full `rsync` to make sure data is consistent. This can take a very long time with large files, so this backend is not suitable to store large VM images. @@ -36,7 +39,7 @@ GlusterFS Volume. GlusterFS transport: `tcp`, `unix` or `rdma` -.Configuration Example ('/etc/pve/storage.cfg') +.Configuration Example (`/etc/pve/storage.cfg`) ---- glusterfs: Gluster server 10.2.3.4 @@ -45,12 +48,14 @@ glusterfs: Gluster content images,iso ---- + File naming conventions ~~~~~~~~~~~~~~~~~~~~~~~ -The directory layout and the file naming conventions are inhertited +The directory layout and the file naming conventions are inherited from the `dir` backend. + Storage Features ~~~~~~~~~~~~~~~~ @@ -64,3 +69,12 @@ snapshot/clone implementation. |images vztempl iso backup |raw qcow2 vmdk |yes |qcow2 |qcow2 |============================================================================== +ifdef::wiki[] + +See Also +~~~~~~~~ + +* link:/wiki/Storage[Storage] + +endif::wiki[] +