From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Chuck Lever <cel@kernel.org>
Subject: Re: NFS workload leaves nfsd threads in D state
Date: Mon, 10 Jul 2023 09:56:34 +0200 [thread overview]
Message-ID: <20230710075634.GA30120@lst.de> (raw)
In-Reply-To: <7A57C7AE-A51A-4254-888B-FE15CA21F9E9@oracle.com>
On Sat, Jul 08, 2023 at 06:30:26PM +0000, Chuck Lever III wrote:
> Hi -
>
> I have a "standard" test of running the git regression suite with
> many threads against an NFS mount. I found that with 6.5-rc, the
> test stalled and several nfsd threads on the server were stuck
> in D state.
Can you paste the exact reproducer here?
> I can reproduce this stall 100% with both an xfs and an ext4
> export, so I bisected with both, and both bisects landed on the
> same commit:
> On system 1: the exports are on top of /dev/mapper and reside on
> an "INTEL SSDSC2BA400G3" SATA device.
>
> On system 2: the exports are on top of /dev/mapper and reside on
> an "INTEL SSDSC2KB240G8" SATA device.
>
> System 1 was where I discovered the stall. System 2 is where I ran
> the bisects.
Ok. I'd be curious if this reproducers without either device mapper
or on a non-SATA device. If you have an easy way to run it in a VM
that'd be great. Otherwise I'll try to recreate it in various
setups if you post the exact reproducer.
next prev parent reply other threads:[~2023-07-10 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 18:30 NFS workload leaves nfsd threads in D state Chuck Lever III
2023-07-09 6:58 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 7:56 ` Christoph Hellwig [this message]
2023-07-10 14:06 ` Chuck Lever III
2023-07-10 15:10 ` Chuck Lever III
2023-07-10 15:18 ` Christoph Hellwig
2023-07-10 17:28 ` Christoph Hellwig
2023-07-10 17:40 ` Chuck Lever III
2023-07-11 12:01 ` Christoph Hellwig
2023-07-12 11:34 ` Chengming Zhou
2023-07-12 13:29 ` Chuck Lever III
2023-07-25 9:57 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-25 13:21 ` Chuck Lever III
2023-07-25 13:34 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20230710075634.GA30120@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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.