diff options
| author | David Sterba <dsterba@suse.com> | 2024-03-25 23:04:39 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2024-03-25 23:13:46 +0100 |
| commit | 2c99d8078f005a2354341d167a93fa065a8bd70e (patch) | |
| tree | d727e4cbee893c6656191d846a342abedf02137c | |
| parent | f240b9f6d04100604dfb605182729f5f49657ff3 (diff) | |
| download | btrfs-progs-2c99d8078f005a2354341d167a93fa065a8bd70e.tar.gz | |
btrfs-progs: prop set: enhance error message when changing subvolume from ro->rw
The error message for ro->rw is not clear enough, add more context for
the received_uuid and send and point to the manual page that explains
more.
Asked at:
https://www.reddit.com/r/btrfs/comments/1bkqor2/received_uuid_error_after_btrfs_send/
[ci skip]
Issue: #763
Signed-off-by: David Sterba <dsterba@suse.com>
| -rw-r--r-- | cmds/property.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/cmds/property.c b/cmds/property.c index ec611c46..8777d144 100644 --- a/cmds/property.c +++ b/cmds/property.c @@ -109,7 +109,9 @@ static int prop_read_only(enum prop_object_type type, do_clear_received_uuid = true; } else { error( -"cannot flip ro->rw with received_uuid set, use force if you really want that"); +"cannot flip ro->rw with received_uuid set, use force option -f if you really want unset the read-only status." +" The value of received_uuid is used for incremental send, consider making a snapshot instead." +" Read more at btrfs-subvolume(8) and Subvolume flags."); return -EPERM; } } |