public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES v2 container] add missing volume activation for hotplug and fsck
Date: Fri, 12 Apr 2024 14:09:08 +0200	[thread overview]
Message-ID: <1712923738.tcdf0bf8tr.astroid@yuna.none> (raw)
In-Reply-To: <20240412110814.46684-1-f.ebner@proxmox.com>

thanks!

On April 12, 2024 1:08 pm, Fiona Ebner wrote:
> Changes in v2:
>     * specify snapname when activating volume for hotplug
>     * add missing activation call for fsck too
> 
> Otherwise those operations would be problematic with certain storages
> like LVM after shutting down a container (which deactivates the
> volumes).
> 
> Fiona Ebner (3):
>   mountpoint mount: activate PVE-managed volumes during preparation
>   pct: fsck: also unmap when fsck command failed
>   pct: fsck: add missing call to activate volume
> 
>  src/PVE/CLI/pct.pm | 13 +++++++++++--
>  src/PVE/LXC.pm     |  1 +
>  2 files changed, 12 insertions(+), 2 deletions(-)
> 
> -- 
> 2.39.2
> 
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 
> 




      parent reply	other threads:[~2024-04-12 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 11:08 [pve-devel] " Fiona Ebner
2024-04-12 11:08 ` [pve-devel] [PATCH v2 container 1/3] mountpoint mount: activate PVE-managed volumes during preparation Fiona Ebner
2024-04-12 11:08 ` [pve-devel] [PATCH v2 container 2/3] pct: fsck: also unmap when fsck command failed Fiona Ebner
2024-04-12 11:08 ` [pve-devel] [PATCH v2 container 3/3] pct: fsck: add missing call to activate volume Fiona Ebner
2024-04-12 12:09 ` Fabian Grünbichler [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=1712923738.tcdf0bf8tr.astroid@yuna.none \
    --to=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal