yes dmesg shows the following:
...
[23661.367449] rbd: rbd12: failed to lock header: -13
[23661.367968] rbd: rbd2: no lock owners detected
[23661.369306] rbd: rbd11: no lock owners detected
[23661.370068] rbd: rbd11: breaking header lock owned by client21473520
[23661.370518] rbd: rbd11: blacklist of client21473520 failed: -13
[23661.370519] rbd: rbd11: failed to lock header: -13
[23661.370869] rbd: rbd5: no lock owners detected
[23661.371994] rbd: rbd1: no lock owners detected
[23661.372546] rbd: rbd1: breaking header lock owned by client21473520
[23661.373058] rbd: rbd1: blacklist of client21473520 failed: -13
[23661.373059] rbd: rbd1: failed to lock header: -13
[23661.374111] rbd: rbd2: breaking header lock owned by client21473520
[23661.374485] rbd: rbd4: no lock owners detected
[23661.375210] rbd: rbd4: breaking header lock owned by client21473520
[23661.375701] rbd: rbd4: blacklist of client21473520 failed: -13
[23661.375702] rbd: rbd4: failed to lock header: -13
[23661.376881] rbd: rbd5: breaking header lock owned by client21473520
[23661.381151] rbd: rbd2: blacklist of client21473520 failed: -13
[23661.385151] rbd: rbd5: blacklist of client21473520 failed: -13
[23661.388279] rbd: rbd2: failed to lock header: -13
________________________________
From: Ilya Dryomov <idryomov@xxxxxxxxx>
Sent: Tuesday, May 24, 2022 5:53:21 PM
To: Sopena Ballesteros Manuel
Cc: ceph-users@xxxxxxx
Subject: Re: rbd command hangs
On Tue, May 24, 2022 at 5:20 PM Sopena Ballesteros Manuel
<manuel.sopena@xxxxxxx> wrote:
>
> Hi Ilya,
>
>
> thank you very much for your prompt response,
>
>
> Any rbd command variation is affected (mapping device included)
>
> We are using a physical machine (no container involved)
>
>
> Below is the output of the running strace as suggested:
>
>
> nid001388:/usr/src/linux # strace -f rbd -n client.noir -o noudev map noir-nvme-meta/nid001388
> execve("/usr/bin/rbd", ["rbd", "-n", "client.noir", "-o", "noudev", "map", "noir-nvme-meta/nid001388"], 0x7ffc33caafe8 /* 63 vars */) = 0
>
> [...]
>
> [pid 28954] openat(AT_FDCWD, "/sys/bus/rbd/add_single_major", O_WRONLY) = 6
> [pid 28954] write(6, "148.187.20.141:6789 name=noir,ke"..., 72 <unfinished ...>
OK, it appears to be stuck in the kernel, attempting to map the image.
Is there anything in dmesg?
Thanks,
Ilya
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
