all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Lukas Sichert" <l.sichert@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH storage v9 1/5] lvm: saferemove: keep LVs where zero-out failed for manual zero-out
Date: Thu, 16 Jul 2026 11:37:07 +0200	[thread overview]
Message-ID: <DJZW7KDTXJXN.O8HYS0IB7CVF@proxmox.com> (raw)
In-Reply-To: <20260713160008.121125-2-l.sichert@proxmox.com>

On Mon Jul 13, 2026 at 6:00 PM CEST, Lukas Sichert wrote:

[snip]

>              eval {
>                  run_command(
>                      $cmd,
> @@ -345,8 +389,7 @@ my sub free_lvm_volumes_locked {
>              }
>  
>              my $cmd = ['blkdiscard', $lvmpath, '-v', '--zeroout', '--step', "${stepsize}"];
> -            eval { run_command($cmd); };
> -            warn $@ if $@;
> +            run_command($cmd);

[marker]

>          }
>      };
>  
> @@ -368,18 +411,33 @@ my sub free_lvm_volumes_locked {
>                  errmsg => "can't refresh LV '$lvmpath' to zero-out its data",
>              );
>  
> -            $secure_delete_cmd->($lvmpath);
> +            eval { $secure_delete_cmd->($lvmpath); };

I haven't tested this (yet), but I think this is problematic. Since the
call at [marker] dies, the if branch below would be entered, which would
then die again, exiting the per-volume loop. If the cleanup of a single
volume failed, wouldn't this result in all remaining volumes not being
touched at all, leaving leftover volumes that have not been cleaned up
and that are also not visible in the UI (I think?) because the regex in
`list_images` does not match them. So you'd have volumes consuming space
while being leftovers from a failed cleanup.

Even though 3/5 structures this a bit differently, this problem still
remains. Hope I'm not missing anything here. I think a fix could be to
accumulate errors from cleanups (so all iterations) and then die once
(?)

> +            if (my $cleanup_err = $@) {
> +                my $failed_name =
> +                    eval { cleanup_failed_lvm_volume($class, $scfg, $storeid, $vg, $name) };
> +                if (my $cleanup_failed_err = $@) {
> +                    log_warn(
> +                        "rename failed for '$vg/del-$name' to failed cleanup volume:"
> +                            . " $cleanup_failed_err",
> +                    );
> +                    die "cleanup failed for lv $name: $cleanup_err\n";
> +                }
>  
> -            $class->cluster_lock_storage(
> -                $storeid,
> -                $scfg->{shared},
> -                undef,
> -                sub {
> -                    my $cmd = ['/sbin/lvremove', '-f', "$vg/del-$name"];
> -                    run_command($cmd, errmsg => "lvremove '$vg/del-$name' error");
> -                },
> -            );
> -            print "successfully removed volume $name ($vg/del-$name)\n";
> +                die
> +                    "cleanup failed for lv $name, renamed to '$vg/$failed_name': $cleanup_err\n";

[snip]




  parent reply	other threads:[~2026-07-16  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 16:00 [PATCH docs/manager/storage v9 0/5] fix #7339: lvmthick: add option to free storage for deleted VMs Lukas Sichert
2026-07-13 16:00 ` [PATCH storage v9 1/5] lvm: saferemove: keep LVs where zero-out failed for manual zero-out Lukas Sichert
2026-07-15 10:26   ` Fiona Ebner
2026-07-16  9:37   ` Michael Köppl [this message]
2026-07-13 16:00 ` [PATCH storage v9 2/5] lvm: saferemove: zero out volumes range by range Lukas Sichert
2026-07-15 10:26   ` Fiona Ebner
2026-07-13 16:00 ` [PATCH storage v9 3/5] fix #7339: lvm: add discard action for removed volumes Lukas Sichert
2026-07-15 10:26   ` Fiona Ebner
2026-07-16 10:46     ` Lukas Sichert
2026-07-13 16:00 ` [PATCH manager v9 4/5] fix #7339: lvm: add discard-on-remove option to UI Lukas Sichert
2026-07-15 10:26   ` Fiona Ebner
2026-07-16  8:49   ` Michael Köppl
2026-07-13 16:00 ` [PATCH docs v9 5/5] fix #7339: lvm: document discard option Lukas Sichert
2026-07-15 10:26   ` Fiona 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=DJZW7KDTXJXN.O8HYS0IB7CVF@proxmox.com \
    --to=m.koeppl@proxmox.com \
    --cc=l.sichert@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal