doc/rados: rewrite "FileStore" section

This PR makes minor improvements to the
syntax of the sentences in the "FileStore"
material in the Configuration chapter of
the RADOS manual.

Signed-off-by: Zac Dover <zac.dover@gmail.com>
This commit is contained in:
Zac Dover 2021-08-05 07:57:24 +10:00
parent 547332a629
commit 413eaa575e

View File

@ -66,19 +66,19 @@ For more information, see :doc:`bluestore-config-ref` and :doc:`/rados/operation
FileStore FileStore
--------- ---------
FileStore is the legacy approach to storing objects in Ceph. It FileStore is the legacy approach to storing objects in Ceph. It
relies on a standard file system (normally XFS) in combination with a relies on a standard file system (normally XFS) in combination with a
key/value database (traditionally LevelDB, now RocksDB) for some key/value database (traditionally LevelDB, now RocksDB) for some
metadata. metadata.
FileStore is well-tested and widely used in production but suffers FileStore is well-tested and widely used in production. However, it
from many performance deficiencies due to its overall design and suffers from many performance deficiencies due to its overall design
reliance on a traditional file system for storing object data. and its reliance on a traditional file system for storing object data.
Although FileStore is generally capable of functioning on most Although FileStore is capable of functioning on most POSIX-compatible
POSIX-compatible file systems (including btrfs and ext4), we only file systems (including btrfs and ext4), we recommend that only the
recommend that XFS be used. Both btrfs and ext4 have known bugs and XFS file system be used with Ceph. Both btrfs and ext4 have known bugs and
deficiencies and their use may lead to data loss. By default all Ceph deficiencies and their use may lead to data loss. By default, all Ceph
provisioning tools will use XFS. provisioning tools use XFS.
For more information, see :doc:`filestore-config-ref`. For more information, see :doc:`filestore-config-ref`.