From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: Re: [pve-devel] [PATCH storage v3 1/4] btrfs: add helper to iterate over snapshots of a subvolume
Date: Wed, 19 Feb 2025 11:17:26 +0100 [thread overview]
Message-ID: <6fddea71-8e9c-4e50-8175-72e24986e214@proxmox.com> (raw)
In-Reply-To: <20250219095848.129788-1-m.sandoval@proxmox.com>
Am 19.02.25 um 10:58 schrieb Maximiliano Sandoval:
> In this context a subvolume means a BTRFS subvolume.
> `$volume\@$snap_name` would be for example
> `btrfs_volume/images/102/vm-102-disk-0@snap_name`.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
>
> Differences from v2:
> - Split into multiple commits
> - Simplify patch
> - Use only the snapshot name in the callback of the helper
>
> Differences from v1:
> - Add a helper to run callback on each snapshot.
>
> src/PVE/Storage/BTRFSPlugin.pm | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/src/PVE/Storage/BTRFSPlugin.pm b/src/PVE/Storage/BTRFSPlugin.pm
> index cadd9d1..43f797a 100644
> --- a/src/PVE/Storage/BTRFSPlugin.pm
> +++ b/src/PVE/Storage/BTRFSPlugin.pm
> @@ -419,6 +419,20 @@ my sub foreach_subvol : prototype($$) {
> })
> }
>
> +# Calls `$code->($volume, $snap_name)` for each snapshot of the BTRFS subvolume.
> +my sub foreach_snapshot_of_subvol : prototype($$) {
> + my ($subvol, $code) = @_;
> +
> + my $basename = basename($subvol);
> + my $dir = dirname($subvol);
> + foreach_subvol($dir, sub {
We're getting there, but:
This helper still is named incorrectly. I'd like to have the helper and
the regex be named correctly (not your fault, but it just gets more
confusing if there are more users). You can change the helper to only
operate on a given subvolume, because that is the only use case we have.
I.e. merge your wrapper and the original helper.
I'd also name it foreach_snapshot_of_subvolume() to better differentiate
it from the 'subvol' format, and path_is_subvolume() already uses the
word 'subvolume'.
> + my ($volume, $name, $snap) = @_;
> + return if $name ne $basename;
> + return if !defined $snap;
> + $code->($snap);
> + });
> +}
> +
> sub free_image {
> my ($class, $storeid, $scfg, $volname, $isBase, $_format) = @_;
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-02-19 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 9:58 Maximiliano Sandoval
2025-02-19 9:58 ` [pve-devel] [PATCH storage v3 2/4] fix #3873: btrfs: use foreach_snapshot_of_subvol helper in volume_export Maximiliano Sandoval
2025-02-19 9:58 ` [pve-devel] [PATCH storage v3 3/4] btrfs: use foreach_snapshot_of_subvol helper in free_image Maximiliano Sandoval
2025-02-19 9:58 ` [pve-devel] [PATCH storage v3 4/4] btrfs: forcefully set image to readwrite Maximiliano Sandoval
2025-02-19 10:17 ` Fiona Ebner [this message]
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=6fddea71-8e9c-4e50-8175-72e24986e214@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.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.