Hi, On Fri, Jul 24, 2020 at 12:37:38PM -0400, Jason Dillaman wrote:
On Fri, Jul 24, 2020 at 10:45 AM Herbert Alexander Faleiros <herbert@registro.br> wrote:
On Fri, Jul 24, 2020 at 07:28:07PM +0500, Alexander E. Patrakov wrote:
On Fri, Jul 24, 2020 at 6:01 PM Herbert Alexander Faleiros <herbert@registro.br> wrote:
Hi,
is there any way to fix it instead a reboot?
[128632.995249] block nbd0: Possible stuck request 00000000b14a04af: control (read@2097152,4096B). Runtime 9540 seconds [128663.718993] block nbd0: Possible stuck request 00000000b14a04af: control (read@2097152,4096B). Runtime 9570 seconds [128694.434774] block nbd0: Possible stuck request 00000000b14a04af: control (read@2097152,4096B). Runtime 9600 seconds [128725.154515] block nbd0: Possible stuck request 00000000b14a04af: control (read@2097152,4096B). Runtime 9630 seconds
# ceph -v ceph version 12.2.13 (584a20eb0237c657dc0567da126be145106aa47e) luminous (stable)
# rbd-nbd list-mapped #
# uname -r 5.4.52-050452-generic
Not enough data to troubleshoot this. Is the rbd-nbd process running?
I.e.:
# cat /proc/partitions # ps axww | grep nbd
no nbd on /proc/partitions, ps shows only:
root 192324 0.0 0.0 0 0 ? I< 07:12 0:00 [knbd0-recv]
You can restart the "rbd-nbd" daemon by running "rbd-nbd map --device /dev/nbd0 <image-spec>"
works, but when I try to unmap, the command block the terminal and never end (I cannot even kill it). Same with nbd-client. Detail: only happens with journaling enabled. -- Herbert