all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Fabian Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v3 storage qemu-server container 0/9] move disk or volume to other guests
Date: Tue, 2 Nov 2021 15:36:40 +0100	[thread overview]
Message-ID: <79ae0f11-b5d7-2c5f-5ab6-e1e17cd8e7e5@proxmox.com> (raw)
In-Reply-To: <e169fddf-3c71-b2a2-5ea2-b9e85820d588@proxmox.com>



On 10/27/21 13:55, Fabian Ebner wrote:
> Nice work! For all patches except #8 it's only nits from my side, so those are:
> 
> Reviewed-by: Fabian Ebner <f.ebner@proxmox.com>
> Tested-by: Fabian Ebner <f.ebner@proxmox.com>
> 
> 
> I did run into one strange issue with RBD upon destroying a VM, but it didn't pop up consistently and maybe it's just my cluster (all VMs were powered off):
> 
> root@pve701 ~ # qm clone 12345 142
> /dev/rbd0
> create linked clone of drive scsi0 (rbdkvm:base-12345-disk-0)
> clone base-12345-disk-0: base-12345-disk-0 snapname __base__ to vm-142-disk-0
> root@pve701 ~ # qm move_disk 142 scsi0 --target-vmid 111 --target-disk scsi3
> moving disk 'scsi0' from VM '142' to '111'
> removing disk 'scsi0' from VM '142' config
> update VM 111: -scsi3 rbdkvm:base-12345-disk-0/vm-111-disk-0,size=4G
> /dev/rbd1
> root@pve701 ~ # qm move_disk 111 scsi3 --target-vmid 142 --target-disk scsi3
> moving disk 'scsi3' from VM '111' to '142'
> removing disk 'scsi3' from VM '111' config
> update VM 142: -scsi3 rbdkvm:base-12345-disk-0/vm-142-disk-0,size=4G
> /dev/rbd2
> root@pve701 ~ # qm destroy 142
> 2021-10-27T12:17:13.202+0200 7f8b00d0e700 -1 librbd::image::PreRemoveRequest: 0x55e08f1cac30 check_image_watchers: image has watchers - not removing
> Removing image: 0% complete...failed.
> rbd: error: image still has watchers
> Could not remove disk 'rbdkvm:base-12345-disk-0/vm-142-disk-0', check manually: rbd rm 'base-12345-disk-0/vm-142-disk-0' error: rbd: error: image still has watchers

I also came across this issue and it seems that we do not unmap KRBD mounted images prior to renaming them. This also applies to converting a guest to a template. I have it on my TODO list to work on that in an extra patch set.




      reply	other threads:[~2021-11-02 14:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 11:30 Aaron Lauterer
2021-10-21 11:30 ` [pve-devel] [PATCH v3 storage 1/9] storage: add new find_free_volname Aaron Lauterer
2021-10-27 10:33   ` Fabian Ebner
2021-10-21 11:30 ` [pve-devel] [PATCH v3 storage 2/9] add disk rename feature Aaron Lauterer
2021-10-27 10:34   ` Fabian Ebner
2021-10-21 11:30 ` [pve-devel] [PATCH v3 qemu-server 3/9] cli: qm: change move_disk to move-disk Aaron Lauterer
2021-10-21 11:30 ` [pve-devel] [PATCH v3 qemu-server 4/9] Drive: add valid_drive_names_with_unused Aaron Lauterer
2021-10-21 11:30 ` [pve-devel] [PATCH v3 qemu-server 5/9] api: move-disk: add move to other VM Aaron Lauterer
2021-10-27 10:59   ` Fabian Ebner
2021-10-21 11:30 ` [pve-devel] [PATCH v3 qemu-server 6/9] api: move-disk: cleanup very long lines Aaron Lauterer
2021-10-21 11:30 ` [pve-devel] [PATCH v3 container 7/9] cli: pct: change move_volume to move-volume Aaron Lauterer
2021-10-21 11:30 ` [pve-devel] [PATCH v3 container 8/9] api: move-volume: add move to another container Aaron Lauterer
2021-10-27 11:44   ` Fabian Ebner
2021-10-21 11:30 ` [pve-devel] [PATCH v3 container 9/9] api: move-volume: cleanup very long lines Aaron Lauterer
2021-10-27 11:55 ` [pve-devel] [PATCH v3 storage qemu-server container 0/9] move disk or volume to other guests Fabian Ebner
2021-11-02 14:36   ` Aaron Lauterer [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=79ae0f11-b5d7-2c5f-5ab6-e1e17cd8e7e5@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=f.ebner@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