From: Adam Kupczyk Date: Wed, 1 Jul 2020 21:09:17 +0000 (+0200) Subject: os/bluestore: Add documentation for large bluefs log recovery X-Git-Tag: v15.2.5~85^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c861dc12fda9d1e2bfd520da2b66966298213eeb;p=ceph.git os/bluestore: Add documentation for large bluefs log recovery Adds additional paragraph to ceph-bluestore-tool documentation, describing how to use *special* options --bluefs_replay_recovery and --bluefs_replay_recovery_disable_compact to recover large bluefs log. Fixes: https://tracker.ceph.com/issues/46552 Signed-off-by: Adam Kupczyk (cherry-picked from commit d7a49b0005501427bb9c9a66d03b723227078349) --- diff --git a/doc/man/8/ceph-bluestore-tool.rst b/doc/man/8/ceph-bluestore-tool.rst index 2bc951ebd13c..af56cd759653 100644 --- a/doc/man/8/ceph-bluestore-tool.rst +++ b/doc/man/8/ceph-bluestore-tool.rst @@ -158,6 +158,21 @@ BlueStore OSD with the *prime-osd-dir* command:: ceph-bluestore-tool prime-osd-dir --dev *main device* --path /var/lib/ceph/osd/ceph-*id* +BlueFS log rescue +===================== + +Some versions of BlueStore were susceptible to BlueFS log growing extremaly large - +beyond the point of making booting OSD impossible. This state is indicated by +booting that takes very long and fails in _replay function. + +This can be fixed by:: + ceph-bluestore-tool fsck --path *osd path* --bluefs_replay_recovery=true + +It is advised to first check if rescue process would be successfull:: + ceph-bluestore-tool fsck --path *osd path* \ + --bluefs_replay_recovery=true --bluefs_replay_recovery_disable_compact=true + +If above fsck is successfull fix procedure can be applied. Availability ============