From: Emmanuel Ameh Date: Tue, 9 Jun 2026 12:34:31 +0000 (+0100) Subject: doc/rados/configuration: Fix FileStore contradiction in journal-ref.rst X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=be52c92ace53387cb578a938c82cee6af4689261;p=ceph.git doc/rados/configuration: Fix FileStore contradiction in journal-ref.rst The page carried a deprecation warning on line 4 stating FileStore "is no longer supported" but line 10 said "Filestore is preferred for new deployments" -- a direct contradiction. Fix by: - Expanding the warning to explicitly state FileStore must not be used for new deployments and to use BlueStore instead - Updating the intro paragraph to reflect that BlueStore is the default and recommended back end, and that this page is for pre-existing Filestore OSDs pending migration only Fixes: https://tracker.ceph.com/issues/77183 Signed-off-by: Emmanuel Ameh --- diff --git a/doc/rados/configuration/journal-ref.rst b/doc/rados/configuration/journal-ref.rst index ea87f9ac9c3..7bb72238750 100644 --- a/doc/rados/configuration/journal-ref.rst +++ b/doc/rados/configuration/journal-ref.rst @@ -1,34 +1,13 @@ ========================== Journal Config Reference ========================== -.. warning:: Filestore has been deprecated in the Reef release and is no longer supported. -.. index:: journal; journal configuration - -Filestore OSDs use a journal for two reasons: speed and consistency. Note -that since Luminous, the BlueStore OSD back end has been preferred and default. -This information is provided for pre-existing OSDs and for rare situations where -Filestore is preferred for new deployments. +.. warning:: Filestore is not supported. Migrate existing Filestore OSDs to + BlueStore. See :ref:`rados_operations_bluestore_migration`. -- **Speed:** The journal enables the Ceph OSD Daemon to commit small writes - quickly. Ceph writes small, random I/O to the journal sequentially, which - tends to speed up bursty workloads by allowing the backing file system more - time to coalesce writes. The Ceph OSD Daemon's journal, however, can lead - to spiky performance with short spurts of high-speed writes followed by - periods without any write progress as the file system catches up to the - journal. - -- **Consistency:** Ceph OSD Daemons require a file system interface that - guarantees atomic compound operations. Ceph OSD Daemons write a description - of the operation to the journal and apply the operation to the file system. - This enables atomic updates to an object (for example, placement group - metadata). Every few seconds--between ``filestore max sync interval`` and - ``filestore min sync interval``--the Ceph OSD Daemon stops writes and - synchronizes the journal with the file system, allowing Ceph OSD Daemons to - trim operations from the journal and reuse the space. On failure, Ceph - OSD Daemons replay the journal starting after the last synchronization - operation. +.. index:: journal; journal configuration -Ceph OSD Daemons recognize the following journal settings: +The following journal settings are provided for reference to assist with +migration of existing Filestore OSDs to BlueStore. .. confval:: journal_dio .. confval:: journal_aio