On Tue, 30 Apr 2019 at 18:50, Alwin Antreich <a.antre...@proxmox.com> wrote: > On Tue, Apr 30, 2019 at 03:12:58PM +0700, Igor Podlesny wrote: [...] > > Obviously > > won't > > work -- if RBD's client is a running instance (aka process) of /usr/bin/kvm. > True, with 'kubelet' I was mistakenly thinking about containers. ;)
I see but it was just an example of "rbd lock list" output. > With normal operation a RBD image is used by the VM with the same ID in > its name. So when the KVM process with the ID isn't running anymore on > the client shown by 'rbd lock list' > (eg. '/usr/bin/kvm -id 100 -name testVM' ...), then the lock should be > old. > > And yes, with the qemu 'info block' you can verify if a kvm process is > using the image, irregardless of the VMID. On a default Proxmox VE setup > there is no other client besides KVM, that uses librbd to connect to the > RBD images. Thank you but still I think it's not any precise. As I explained: > > Moreover, it might be the case that one did check with qemu monitor's > > "info block" all the running instances and didn't find references to > > image in question. > > So I'm looking for bullet proof and better direct way to use info > > given by "rbd lock list". Guesswork takes too much time and efforts. If there's no direct way to find the client using "rbd lock list" info -- it's a huge drawback. And I'm curious to know what those numbers in the output are anyways. ;) -- End of message. Next message? _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
