From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 2/2] btrfs-progs: doc: add extra note on flipping read-only on received subvolumes
Date: Fri, 10 Sep 2021 14:03:35 +0800 [thread overview]
Message-ID: <20210910060335.38617-3-wqu@suse.com> (raw)
In-Reply-To: <20210910060335.38617-1-wqu@suse.com>
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
Documentation/btrfs-property.asciidoc | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/btrfs-property.asciidoc b/Documentation/btrfs-property.asciidoc
index 4796083378e4..8949ea22edae 100644
--- a/Documentation/btrfs-property.asciidoc
+++ b/Documentation/btrfs-property.asciidoc
@@ -42,6 +42,12 @@ the following:
ro::::
read-only flag of subvolume: true or false
++
+NOTE: For recevied subvolumes, flipping from read-only to read-write will
+either remove the recevied UUID and prevent future incremental receive
+(on newer kernels), or cause future data corruption and recevie failure
+(on older kernels).
+
label::::
label of the filesystem. For an unmounted filesystem, provide a path to a block
device as object. For a mounted filesystem, specify a mount point.
--
2.33.0
next prev parent reply other threads:[~2021-09-10 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 6:03 [PATCH 0/2] btrfs-progs: add educational warning for flipping RO to RW on recevied subvolumes Qu Wenruo
2021-09-10 6:03 ` [PATCH 1/2] btrfs-progs: do extra warning when setting ro false on received subvolume Qu Wenruo
2021-09-10 6:36 ` Nikolay Borisov
2021-09-10 7:28 ` Qu Wenruo
2021-09-10 9:38 ` Graham Cobb
2021-09-10 6:03 ` Qu Wenruo [this message]
2021-09-10 6:33 ` [PATCH 2/2] btrfs-progs: doc: add extra note on flipping read-only on received subvolumes Nikolay Borisov
2021-09-10 7:30 ` Qu Wenruo
2021-09-10 9:48 ` Graham Cobb
2021-09-10 9:45 ` David Sterba
2021-09-10 9:59 ` Qu Wenruo
2021-09-10 10:50 ` Nikolay Borisov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210910060335.38617-3-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox