all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] superseded: [PATCH container/qemu-server v6 0/7] fix #3711 and adapt drive detach/remove behavior
Date: Tue, 27 May 2025 18:05:07 +0200	[thread overview]
Message-ID: <5374d416-ed04-4939-9c27-0e1dc8ae4602@proxmox.com> (raw)
In-Reply-To: <20250520090818.44881-1-m.koeppl@proxmox.com>

Supersed-by: https://lore.proxmox.com/pve-devel/20250527160140.230174-1 m.koeppl@proxmox.com/T

On 5/20/25 11:08, Michael Köppl wrote:
> This series aims to fix #3711 [0] and streamline the detach/remove
> behavior around volumes that are either mounted into a container or
> attached to a VM as a hard disk. It is a continuation of a series from
> 2022 [1], but makes the following changes:
> 
> Changes v5 -> v6:
> - Fix links in cover letter
> - Use Originally-by instead of Co-authored-by
> - Add documentation for the second patch regarding the use of
>   $mp->{volume} instead of $conf->{$opt}
> - Note that no functional changes are intended for the the second patch
> 
> Changes v4 -> v5:
> - Always ignore errors that originate from a removed storage and
>   continue with destruction of a container or removal of a volume, 
>   instead of adding an option to ignore these errors.
> - Remove web UI checkbox
> - Remove formatting patch
> - Additionally allow removing a mount point with a removed storage
>   from a running container (previously hotplug removal was not possible)
> - Fix style nits from v4 review
> - Print warnings for any errors that occur instead of ignoring them
> - Add explicit check if storage still exists when destroying a container
>   to differentiate between that case and other error cases (which should
>   still fail)
> 
> The first change also means that this patch series should be held back
> until PVE 9. In the original patch series the option to ignore these
> errors was made to avoid breaking existing behavior. After some off-list
> discussion it seems more reasonable to avoid an additional option and
> instead allow users to remove containers with mount points even if the
> underlying storage of the mount point was removed.
> 
> Where at least some of the implementation was taken from the previous
> series, the patch was marked to be Originally-by by the original author.
> 
> [0] https://bugzilla.proxmox.com/show_bug.cgi?id=3711
> [1] https://lore.proxmox.com/pve-devel/20221125144008.2988072-1-s.hrdlicka@proxmox.com/t/#
> 
> pve-container:
> 
> Michael Köppl (4):
>   fix #3711: lxc: print warning if storage for mounted volume does not
>     exist anymore
>   config: apply_pending: get unused volid through parse_volume()
>   fix #3711: lxc: allow removing unused mp if storage no longer exists
>   add linked clone check when destroying container
> 
>  src/PVE/LXC.pm        | 24 +++++++++++++++++++++++-
>  src/PVE/LXC/Config.pm | 25 ++++++++++++++++++++-----
>  2 files changed, 43 insertions(+), 6 deletions(-)
> 
> 
> qemu-server:
> 
> Michael Köppl (3):
>   adapt linked clone check to not die if an error occurs during check
>   print warning for PVE::Storage::path errors instead of failing
>   mark volumes pending detach as unused if storage was removed
> 
>  PVE/QemuServer.pm | 16 +++++++++++-----
>  1 file changed, 11 insertions(+), 5 deletions(-)
> 
> 
> Summary over all repositories:
>   3 files changed, 54 insertions(+), 11 deletions(-)
> 



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

      parent reply	other threads:[~2025-05-27 16:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  9:08 [pve-devel] " Michael Köppl
2025-05-20  9:08 ` [pve-devel] [PATCH container v6 1/4] fix #3711: lxc: print warning if storage for mounted volume does not exist anymore Michael Köppl
2025-05-20 13:33   ` Fiona Ebner
2025-05-22  6:08     ` Thomas Lamprecht
2025-05-27  7:37       ` Michael Köppl
2025-05-22  6:17   ` Thomas Lamprecht
2025-05-27  7:29     ` Michael Köppl via pve-devel
2025-05-20  9:08 ` [pve-devel] [PATCH container v6 2/4] config: apply_pending: get unused volid through parse_volume() Michael Köppl
2025-05-20 13:45   ` Fiona Ebner
2025-05-20 13:49     ` Fiona Ebner
2025-05-20  9:08 ` [pve-devel] [PATCH container v6 3/4] fix #3711: lxc: allow removing unused mp if storage no longer exists Michael Köppl
2025-05-20 14:03   ` Fiona Ebner
2025-05-27  9:34     ` Michael Köppl
2025-05-27 10:03       ` Fiona Ebner
2025-05-20  9:08 ` [pve-devel] [PATCH container v6 4/4] add linked clone check when destroying container Michael Köppl
2025-05-20 14:13   ` Fiona Ebner
2025-05-20  9:08 ` [pve-devel] [PATCH qemu-server v6 1/3] adapt linked clone check to not die if an error occurs during check Michael Köppl
2025-05-21 10:49   ` Fiona Ebner
2025-05-20  9:08 ` [pve-devel] [PATCH qemu-server v6 2/3] print warning for PVE::Storage::path errors instead of failing Michael Köppl
2025-05-21 11:02   ` Fiona Ebner
2025-05-20  9:08 ` [pve-devel] [PATCH qemu-server v6 3/3] mark volumes pending detach as unused if storage was removed Michael Köppl
2025-05-21 11:16   ` Fiona Ebner
2025-05-26 12:24     ` Michael Köppl
2025-05-27 16:05 ` Michael Köppl [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=5374d416-ed04-4939-9c27-0e1dc8ae4602@proxmox.com \
    --to=m.koeppl@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