From: Sagi Grimberg <sagi@grimberg.me>
To: Szymon Scharmach <szymon.scharmach@gmail.com>,
linux-nvme@lists.infradead.org
Subject: Re: "nvme disconnect" for mounted volumes - stuck thread
Date: Mon, 9 Sep 2019 12:31:43 -0700 [thread overview]
Message-ID: <a85e2dc8-f76d-15ab-f86b-7d79af5bd99f@grimberg.me> (raw)
In-Reply-To: <CAKFbMv8u9w7jKB9tux1+4+8xQWdRpA4Y1kArrt6rCX1L0H76sA@mail.gmail.com>
> Hi,
>
> In the deployment scenario i am using we use around 200 NvmeOF volumes
> that are being connected to different initiators and after data have
> been saved - reconnected to different ones.
> nvme cli allows to disconnect volumes that are either mounted or
> umount is in progress which leads threads to end up in uninterruptible
> sleep. (D state)
>
> root 69368 0.0 0.0 6704 640 ? D 09:29 0:00 nvme
> disconnect --nqn=pvc-4f6b7502-cb08-11e9-a2bf-3cfdfeb878d0
> root 69375 0.0 0.0 5920 900 ? D 09:29 0:00
> umount /var/lib/origin/openshift.local.volumes/pods/4f6caee2-cb08-11e9-a2bf-3cfdfe-b878d0/
> volumes/kubernetes.io~csi/pvc-4f6b7502-cb08-11e9-a2bf-3c
Do you have the watchdog hand detector trace to share?
>
> Those threads are stuck in D forever and whole block stack on the node
> becomes unusable.
> Is it the responsibility of nvme-cli or kernel module (nvme_fabrics
> AFAIK) to block 'disconnect' in that case - or is it expected behavior
> (nvme disconnect with force flag maybe) ?
None, I guess it should be something like _netdev fstab entry...
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-09-09 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 10:06 "nvme disconnect" for mounted volumes - stuck thread Szymon Scharmach
2019-09-09 19:31 ` Sagi Grimberg [this message]
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=a85e2dc8-f76d-15ab-f86b-7d79af5bd99f@grimberg.me \
--to=sagi@grimberg.me \
--cc=linux-nvme@lists.infradead.org \
--cc=szymon.scharmach@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).