From: Josef Bacik <josef@toxicpanda.com>
To: Mark Harmstone <maharmstone@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs-progs: set subvol uuids when converting
Date: Fri, 19 Jul 2024 16:20:40 -0400 [thread overview]
Message-ID: <20240719202040.GA2312632@perftesting> (raw)
In-Reply-To: <20240719150343.3992904-2-maharmstone@fb.com>
On Fri, Jul 19, 2024 at 04:03:24PM +0100, Mark Harmstone wrote:
> Currently when using btrfs-convert, neither the main subvolume nor the
> image subvolume get uuids assigned, nor is the uuid tree created.
>
> Signed-off-by: Mark Harmstone <maharmstone@fb.com>
> ---
> common/root-tree-utils.c | 29 +++++++++++++++++++++++++++++
> common/root-tree-utils.h | 1 +
> convert/common.c | 14 +++++++++-----
> convert/main.c | 8 +++++++-
> mkfs/main.c | 29 -----------------------------
> 5 files changed, 46 insertions(+), 35 deletions(-)
>
> diff --git a/common/root-tree-utils.c b/common/root-tree-utils.c
> index f9343304..9495178c 100644
> --- a/common/root-tree-utils.c
> +++ b/common/root-tree-utils.c
> @@ -59,6 +59,35 @@ error:
> return ret;
> }
>
> +int create_uuid_tree(struct btrfs_trans_handle *trans)
If we're exporting a new thing then it needs to be renamed to
btrfs_create_uuid_tree.
Also a convert test for this would be good, to validate we're getting the UUID
tree on convert. Thanks,
Josef
next prev parent reply other threads:[~2024-07-19 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 15:03 [PATCH 1/2] btrfs-progs: add set_uuid param to btrfs_make_subvolume Mark Harmstone
2024-07-19 15:03 ` [PATCH 2/2] btrfs-progs: set subvol uuids when converting Mark Harmstone
2024-07-19 20:20 ` Josef Bacik [this message]
2024-07-19 22:28 ` Qu Wenruo
2024-07-26 17:30 ` David Sterba
2024-07-19 20:21 ` [PATCH 1/2] btrfs-progs: add set_uuid param to btrfs_make_subvolume Josef Bacik
2024-07-19 22:23 ` Qu Wenruo
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=20240719202040.GA2312632@perftesting \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=maharmstone@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.