From fc1532241e475239c1166561ea7adeaf5ee08617 Mon Sep 17 00:00:00 2001 From: Jos Collin Date: Thu, 19 Jun 2025 13:15:19 +0530 Subject: [PATCH] doc: drop manual remote snapshotting Drop the word 'manually' from the doc, as this could also happen via snap-schedule. Signed-off-by: Jos Collin --- doc/cephfs/cephfs-mirroring.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/cephfs/cephfs-mirroring.rst b/doc/cephfs/cephfs-mirroring.rst index 147100c9e31d..04656bd4b969 100644 --- a/doc/cephfs/cephfs-mirroring.rst +++ b/doc/cephfs/cephfs-mirroring.rst @@ -439,7 +439,7 @@ This allows a user to add a non-existent directory for synchronization. The mirr will mark such a directory as failed and retry (less frequently). When the directory is created, the mirror daemon will clear the failed state upon successful synchronization. -Adding a new snapshot or a new directory manually in the ``.snap`` directory of the +Adding a new snapshot or a new directory in the ``.snap`` directory of the remote filesystem will result in failed status of the corresponding configured directory. In the remote filesystem:: @@ -473,6 +473,9 @@ In the remote filesystem:: When the snapshot or the directory is removed from the remote filesystem, the mirror daemon will clear the failed state upon successful synchronization of the pending snapshots, if any. +.. note:: Setting snap-schedule on the remote flle system for directories that are being mirrored will + cause the mirror daemon to report errors like ``invalid metadata``. + .. note:: Treat the remote filesystem as read-only. Nothing is inherently enforced by CephFS. But with the right MDS caps, users would not be able to snapshot directories in the remote file system. -- 2.47.3