From 958e2fc4429ad75fded2716b08acc391c5e46e30 Mon Sep 17 00:00:00 2001 From: David Sterba Date: Wed, 21 Sep 2022 09:55:19 +0200 Subject: [PATCH] btrfs-progs: docs: note about read-only mount for send Clarify that read-only mount is not sufficient. Issue: #493 Signed-off-by: David Sterba --- Documentation/btrfs-send.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/btrfs-send.rst b/Documentation/btrfs-send.rst index 291c537e..4d9c62ec 100644 --- a/Documentation/btrfs-send.rst +++ b/Documentation/btrfs-send.rst @@ -16,7 +16,9 @@ The command operates in two modes: full and incremental. All snapshots involved in one send command must be read-only, and this status cannot be changed as long as there's a running send operation that uses the -snapshot. +snapshot. Read-only mount of the subvolume is not sufficient, there's no way to +guarantee that there won't be any other writable mount of the same subvolume +that would potentially write while send would be running. In the full mode, the entire snapshot data and metadata will end up in the stream.