From: Jos Collin Date: Fri, 5 Jan 2018 06:21:00 +0000 (+0530) Subject: doc: misc fixes X-Git-Tag: v12.2.3~228^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=0f0df7db74069fef8b526c849002f82f9d8087dd;p=ceph.git doc: misc fixes misc fixes for best-practices. Signed-off-by: Jos Collin (cherry picked from commit ecacd1078db5020e6d65436f9d56cc9ed0016666) --- diff --git a/doc/cephfs/best-practices.rst b/doc/cephfs/best-practices.rst index 9efe48cb0976..06a14ec6b8e7 100644 --- a/doc/cephfs/best-practices.rst +++ b/doc/cephfs/best-practices.rst @@ -30,14 +30,15 @@ and **do not use snapshots**. Both of these are the default. Note that creating multiple MDS daemons is fine, as these will simply be used as standbys. However, for best stability you should avoid -adjusting ``max_mds`` upwards, as this would cause multiple +adjusting ``max_mds`` upwards, as this would cause multiple MDS daemons to be active at once. Which client? ------------- -The fuse client is the easiest way to get up to date code, while -the kernel client will often give better performance. +The FUSE client is the most accessible and the easiest to upgrade to the +version of Ceph used by the storage cluster, while the kernel client will +often give better performance. The clients do not always provide equivalent functionality, for example the fuse client supports client-enforced quotas while the kernel client @@ -83,6 +84,5 @@ information as possible. Especially important information: * Any backtraces in the ceph logs from crashes If you are satisfied that you have found a bug, please file it on -http://tracker.ceph.com. For more general queries please write -to the ceph-users mailing list. - +`the tracker `_. For more general queries please write +to the `ceph-users mailing list `_.