From: Dhairya Parmar <dparmar@redhat.com>
Date: Mon, 15 Jun 2026 12:44:16 +0000 (+0530)
Subject: tools/cephfs: document --max-rss usage in first-damage.py
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=d611da1c2513e94e6718ba01e6701db321b33973;p=ceph.git

tools/cephfs: document --max-rss usage in first-damage.py

Partially-Fixes: https://tracker.ceph.com/issues/76422
Signed-off-by: Dhairya Parmar <dparmar@redhat.com>
---

diff --git a/src/tools/cephfs/first-damage.py b/src/tools/cephfs/first-damage.py
index 763ab5af7f6..02483bba507 100644
--- a/src/tools/cephfs/first-damage.py
+++ b/src/tools/cephfs/first-damage.py
@@ -23,6 +23,16 @@
 #
 #    cephfs-journal-tool --rank=<fs_name>:0 event recover_dentries summary
 #
+#    NOTE: Large journal sizes can cause the tool's Resident Set Size (RSS) to
+#          spike significantly. To prevent excessive memory consumption, use the
+#          `--max-rss <bytes>` flag to cap the RSS. 
+#
+#          Avoid setting this value too low, as it will severely degrade runtime
+#          performance and prolong recovery. It is best practice to maintain a memory
+#          buffer of at least 30% of the tool's total budget. For example, if 100 GiB
+#          is to be allotted to the tool, cap the RSS at 70 GiB
+#          (`--max-rss 75161927680`).
+#
 # 4b) If all good so far, reset the journal:
 #
 #    cephfs-journal-tool --rank=<fs_name>:0 journal reset --yes-i-really-really-mean-it