From: Sagi Grimberg <sagi@grimberg.me>
To: Anton Brekhov <anton.brekhov@rsc-tech.ru>,
linux-nvme@lists.infradead.org
Subject: Re: NVMe Over Fabrics Disconnect Kernel error
Date: Sat, 28 Mar 2020 21:14:46 -0700 [thread overview]
Message-ID: <a7da72d0-ed3f-ab5c-a72b-1b0518436a2e@grimberg.me> (raw)
In-Reply-To: <CABY-YC7eHFjb-TpKf2ioPJNhZ8RccYsrR-oU=wmt26z9AUNebg@mail.gmail.com>
> Greetings!
>
> We're using nvme-cli technology with ZFS and Lustre Filesystem on top of it.
> But we constantly come across a kernel error while disconnecting
> remote disks from switched off nodes:
> ```
> [ +0,000089] INFO: task kworker/u593:0:82293 blocked for more than 120 seconds.
> [ +0,001959] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [ +0,001941] kworker/u593:0 D ffff90e8493fe2a0 0 82293 2 0x00000080
> [ +0,000031] Workqueue: nvme-delete-wq nvme_delete_ctrl_work [nvme_core]
> [ +0,000003] Call Trace:
> [ +0,000008] [<ffffffff8177f229>] schedule+0x29/0x70
> [ +0,000010] [<ffffffff81358e85>] blk_mq_freeze_queue_wait+0x75/0xe0
> [ +0,000007] [<ffffffff810c61c0>] ? wake_up_atomic_t+0x30/0x30
> [ +0,000006] [<ffffffff81359cb4>] blk_freeze_queue+0x24/0x50
> [ +0,000009] [<ffffffff8134e0ef>] blk_cleanup_queue+0x7f/0x1b0
> [ +0,000012] [<ffffffffc031158e>] nvme_ns_remove+0x8e/0xb0 [nvme_core]
> [ +0,000011] [<ffffffffc031174b>] nvme_remove_namespaces+0xab/0xf0 [nvme_core]
> [ +0,000012] [<ffffffffc03117e2>] nvme_delete_ctrl_work+0x52/0x80 [nvme_core]
> [ +0,000008] [<ffffffff810bd0ff>] process_one_work+0x17f/0x440
> [ +0,000006] [<ffffffff810be368>] worker_thread+0x278/0x3c0
> [ +0,000006] [<ffffffff810be0f0>] ? manage_workers.isra.26+0x2a0/0x2a0
> [ +0,000005] [<ffffffff810c50d1>] kthread+0xd1/0xe0
> [ +0,000006] [<ffffffff810c5000>] ? insert_kthread_work+0x40/0x40
> [ +0,000006] [<ffffffff8178cd1d>] ret_from_fork_nospec_begin+0x7/0x21
> [ +0,000006] [<ffffffff810c5000>] ? insert_kthread_work+0x40/0x40
> ```
> Nodes characteristics:
> [root@s02p005 ~]# uname -srm
> Linux 3.10.0-1062.1.1.el7.x86_64 x86_64
> [root@s02p005 ~]# cat /etc/redhat-release
> CentOS Linux release 7.7.1908 (Core)
>
> Where're using nvmet_rdma.
> Is there any workaround for such error?
It seems like queue freeze is stuck. Can you share more of the
trace so we can see what else is blocking? If not, when
it reproduces run echo t > /proc/sysrq-trigger and share the
log.
Thanks.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-29 4:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 6:12 NVMe Over Fabrics Disconnect Kernel error Anton Brekhov
2020-03-29 4:14 ` Sagi Grimberg [this message]
2020-03-29 8:50 ` Max Gurtovoy
2020-03-29 11:38 ` Anton Brekhov
2020-03-29 11:56 ` Max Gurtovoy
2020-03-29 14:40 ` Anton Brekhov
2020-03-30 4:38 ` Sagi Grimberg
2020-03-30 8:26 ` Anton Brekhov
2020-03-31 13:26 ` Christoph Hellwig
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=a7da72d0-ed3f-ab5c-a72b-1b0518436a2e@grimberg.me \
--to=sagi@grimberg.me \
--cc=anton.brekhov@rsc-tech.ru \
--cc=linux-nvme@lists.infradead.org \
/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.