From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, d.tschlatscher@proxmox.com
Subject: Re: [pve-devel] [PATCH storage v2 1/2] fix #3972: Remove the .notes file when a backup is deleted
Date: Wed, 18 May 2022 11:08:26 +0200 [thread overview]
Message-ID: <b53f5a27-0161-dae8-21c9-ea0fb738502c@proxmox.com> (raw)
In-Reply-To: <20220512131753.126854-1-d.tschlatscher@proxmox.com>
Looks good to me, just a few suggestions for further improvements.
Am 12.05.22 um 15:17 schrieb Daniel Tschlatscher:
> When a VM or Container backup was deleted, the .notes file was not
> removed, therefore, over time the dump folder would get polluted with
> notes for backups that no longer existed.
> As backup names contain a timestamp and as the notes cannot be reused
> because of this, I think it is safe to just delete them just like we
> do with the .log file.
>
> Furthermore, I sourced the deletion of the log and notes file into a
> new function called "archive_auxiliaries_remove". This change makes it
> easier to remove these files through archive_remove(), but also other
> parts in the code while keeping it DRY.
I like the helper. I think the second sentence above is not needed
though, as that's true for most helper functions ;)
> I saw this change necessary because archive_remove() does not invoke
> external plugins, and doing so might have unintended side effects.
>
IMHO the point is that we have to keep calling vdisk_free() for PBS and
external plugins in the API call. If archive_remove() were designed to
call plugins, I'd argue that the side effects would be intended.
Usually, the plugin knows best what to do.
> Signed-off-by: Daniel Tschlatscher <d.tschlatscher@proxmox.com>
> ---
> PVE/API2/Storage/Content.pm | 5 ++---
> PVE/Storage.pm | 19 +++++++++++++++++--
> 2 files changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/PVE/API2/Storage/Content.pm b/PVE/API2/Storage/Content.pm
> index 8ff858d..41b577c 100644
> --- a/PVE/API2/Storage/Content.pm
> +++ b/PVE/API2/Storage/Content.pm
> @@ -456,9 +456,8 @@ __PACKAGE__->register_method ({
> print "Removed volume '$volid'\n";
> if ($vtype eq 'backup'
> && $path =~ /(.*\/vzdump-\w+-\d+-\d{4}_\d{2}_\d{2}-\d{2}_\d{2}_\d{2})[^\/]+$/) {
> - my $logpath = "$1.log";
> - # try to cleanup our backup log file too, if still existing, #318
> - unlink($logpath) if -e $logpath;
> + # Remove log file #318 and notes file #3972 if they still exist
> + PVE::Storage::archive_auxiliaries_remove($path);
> }
> };
>
> diff --git a/PVE/Storage.pm b/PVE/Storage.pm
> index 72458cf..5317043 100755
> --- a/PVE/Storage.pm
> +++ b/PVE/Storage.pm
> @@ -1566,6 +1566,7 @@ sub archive_info {
>
> if ($volid =~ /^(vzdump-${type}-([1-9][0-9]{2,8})-(\d{4})_(\d{2})_(\d{2})-(\d{2})_(\d{2})_(\d{2}))\.${extension}$/) {
> $info->{logfilename} = "$1.log";
> + $info->{notesfilename} = "$filename.notes";
Nit: Could use PVE::Storage::Plugin::NOTES_EXT
> $info->{vmid} = int($2);
> $info->{ctime} = timelocal($8, $7, $6, $5, $4 - 1, $3);
> $info->{is_std_name} = 1;
> @@ -1585,11 +1586,18 @@ sub archive_remove {
> die "cannot remove protected archive '$archive_path'\n"
> if -e protection_file_path($archive_path);
>
> + unlink $archive_path or die "removing archive $archive_path failed: $!\n";
Not new, but this could be improved by using
unlink $archive_path or $! == ENOENT or die "..."
like we do in other places. That would gracefully handle the case where
two operations raced, e.g. pruning and manual removal. Previously, one
of them would fail, because the file was already gone. Please make that
its own patch if you go for it, thanks!
> +
> + archive_auxiliaries_remove($archive_path);
> +}
> +
> +sub archive_auxiliaries_remove {
> + my ($archive_path) = @_;
> +
> my $dirname = dirname($archive_path);
> my $archive_info = eval { archive_info($archive_path) } // {};
> my $logfn = $archive_info->{logfilename};
> -
> - unlink $archive_path or die "removing archive $archive_path failed: $!\n";
> + my $notesfn = $archive_info->{notesfilename};
>
Style nit: The rest could be turned into a loop to avoid code repetition
like:
for my $type (qw(log notes)) {
my $fn = $archive_info->{"${type}filename"} or next;
my $path = ...
> if (defined($logfn)) {
> my $logpath = "$dirname/$logfn";
> @@ -1597,6 +1605,13 @@ sub archive_remove {
> unlink $logpath or warn "removing log file $logpath failed: $!\n";
Same here with ENOENT
> }
> }
> +
> + if (defined($notesfn)) {
> + my $notespath = "$dirname/$notesfn";
> + if (-e $notespath) {
> + unlink $notespath or warn "removing notes file $notespath failed: $!\n";
and here.
> + }
> + }
> }
>
> sub extract_vzdump_config_tar {
next prev parent reply other threads:[~2022-05-18 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 13:17 Daniel Tschlatscher
2022-05-12 13:17 ` [pve-devel] [PATCH storage v2 2/2] fix #3972: test: Adapt test cases to changes in archive_info Daniel Tschlatscher
2022-05-18 9:08 ` Fabian Ebner
2022-05-18 9:08 ` Fabian Ebner [this message]
2022-05-18 9:16 ` [pve-devel] [PATCH storage v2 1/2] fix #3972: Remove the .notes file when a backup is deleted Fabian Ebner
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=b53f5a27-0161-dae8-21c9-ea0fb738502c@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.tschlatscher@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox