[PVE-User] rbd lock list -- how to track down to client?
a.antreich at proxmox.com
Tue Apr 30 10:02:46 CEST 2019
On Tue, Apr 30, 2019 at 02:30:19PM +0700, Igor Podlesny wrote:
> In most cases I've found people were willing just to remove the lock.
> But as to me it's better try to find if there's no legitimate use
> before doing that.
> So, as an example (at
> > $ rbd lock list cassandra
> > There is 1 exclusive lock on this image.
> > Locker ID Address
> > client.10197 kubelet_lock_magic_nodebr0 10.0.2.5:0/1005447
> How would one find out what's using it?
> The only clear item is IP address (and port number is indicated as "0"
> which isn't any helpful), but obviously host can have tons of RBD
> clients running as well.
> Can 10197 or 1005447 give any cue?
> Also, with Proxmox KVM ID looks as "auto" followed by rather big
> integer. Can it be used for such tracking?
Once you have the client, you connect to it run a 'rbd showmapped' to
see which rbd device is mapped to which image.
More information about the pve-user