From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8CA91EB64DC for ; Mon, 10 Jul 2023 07:56:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232286AbjGJH4n (ORCPT ); Mon, 10 Jul 2023 03:56:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57080 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232294AbjGJH4k (ORCPT ); Mon, 10 Jul 2023 03:56:40 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D8AB9106; Mon, 10 Jul 2023 00:56:38 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 6454D67373; Mon, 10 Jul 2023 09:56:35 +0200 (CEST) Date: Mon, 10 Jul 2023 09:56:34 +0200 From: Christoph Hellwig To: Chuck Lever III Cc: Jens Axboe , Christoph Hellwig , "linux-block@vger.kernel.org" , Linux NFS Mailing List , Chuck Lever Subject: Re: NFS workload leaves nfsd threads in D state Message-ID: <20230710075634.GA30120@lst.de> References: <7A57C7AE-A51A-4254-888B-FE15CA21F9E9@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7A57C7AE-A51A-4254-888B-FE15CA21F9E9@oracle.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org 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.