From nobody Fri May 31 21:10:34 2024 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VrbPg608Mz5LNc8 for ; Fri, 31 May 2024 21:10:47 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VrbPg1QxYz4YZ1 for ; Fri, 31 May 2024 21:10:47 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="M/VSuNcw"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2607:f8b0:4864:20::1031 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-2bfffa3c748so1948507a91.3 for ; Fri, 31 May 2024 14:10:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717189845; x=1717794645; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=jkbO8XinZCFgu/g6mociXTje8yr1zevRMJClucVvgZc=; b=M/VSuNcwfmOjTLWUFh7XMLu/aDeW8OBZ98gK/dvqu+7dObAFRA+hp5nX8pLg6tNGYt 6kXnHYmxF1+TlqSpqdP4r69Pz6gtStF45Uz8RBUy+pgFz/XLD6TCKNM7it2rRMwqrpYf IWvK4rNP6ZsSWxLu3wa430qi4Dgpi4usfvPRArdb5ZCMeMg2L6Sk40egBWwfFsDvdD45 C2oxO/CrShYw5amXwDh8BiiUiA8QPplpVxvjsnTivRS7Lc9qTebzeNJomizwTXOYvAuM 23UUmkEyGDcI0BWTH0pNH77o+4/qdjOYkL+8RhUUsqZm9QVM2+cGB8lGezaue666HTWL LULA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717189845; x=1717794645; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jkbO8XinZCFgu/g6mociXTje8yr1zevRMJClucVvgZc=; b=gM8bUdWPp4AuLB4oewSb06sA0Yatdt/S3en1xrPeR5/ouleDDpc5w2WV/poomK8/8w mtuNB5e+OCPjm26YEtFF+aWd7e81STZo1TJ2fI41lm/weFX9502PdViLOupxvWo7WCuP 6fD1Vt82L4Mi7QpOj/t3TdV6DtqK0/Ry2poCQkAed2UHM0KXRhhM8fkLTH5b0YLfETJe P3YtpNkN3e8fM2vgMfMzcWLgz++OSUdNOM2AHmRJKsrUqiLAdTtm8Jm/1e4zSiQhwpF9 rVF/Ru4DoiZJa5qmMgGJODbVLcqObQ9JpTpi9Obv+C/fj2HNPDWOdvlGB3PtBzlEQEGt BRcg== X-Gm-Message-State: AOJu0Yz0HSGCCmKfgXlt/ipzsCPy6e9sd7nyy+UkIqfxC0GPc+IM9l1j slHiTXdw4FMJre6dgtK0LuWP8iUxPwgCUFWblzsmlc1zX+FGWyyvQP8KEldAYXkT/OLrMsFyZg8 yqvUNuV82pmgSNdZchAOioRCl9g== X-Google-Smtp-Source: AGHT+IEMZ1075G0aBFqUCwADObXHaP2bshaTOJNXncgfu4AQnzqFFDAN4wTyXGIJGKJd6n7NwfWgPer4d9lZzuXK278= X-Received: by 2002:a17:90a:d593:b0:2c1:bb0c:9af4 with SMTP id 98e67ed59e1d1-2c1dc4b479cmr3355620a91.0.1717189845033; Fri, 31 May 2024 14:10:45 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Fri, 31 May 2024 14:10:34 -0700 Message-ID: Subject: Re: NFSv4 hangs on 13.3 To: J David Cc: FreeBSD FS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.994]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; TO_DN_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; TAGGED_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TAGGED_RCPT(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1031:from] X-Rspamd-Queue-Id: 4VrbPg1QxYz4YZ1 On Fri, May 31, 2024 at 1:11=E2=80=AFPM Rick Macklem wrote: > > On Fri, May 31, 2024 at 12:39=E2=80=AFPM J David wrote: > > > > In an attempt to narrow down the problems we have with NFS v4.2, we've > > set up a FreeBSD 13.3 server that mirrors some read-only data from our > > Linux NFS servers. > > > > We are still observing occasional hangs on the FreeBSD 13.3 client mach= ines. > > > > When these hangs occur, anything that touches the mountpoint > > (including "umount -N") hangs indefinitely. There is nothing in dmesg. > > > > The only even slightly informative data I could gather is an "ls > > /mount/point" kstack: > > > > $ sudo procstat -kk 94676 > > PID TID COMM TDNAME KSTACK > > 94676 976876 ls - mi_switch+0xbf > > sleeplk+0xea lockmgr_slock_hard+0x3a5 nfs_lock+0x29 vop_sigdefer+0x2a > > _vn_lock+0x47 vfs_cache_root+0x9d vfs_root_sigdefer+0x35 lookup+0x88a > > namei+0x24a kern_statat+0xf8 sys_fstatat+0x27 amd64_syscall+0x110 > > fast_syscall_common+0xf8 > > > > During this time, the NFS server continues serving other clients, and > > the affected client can access other NFS servers without hanging. > > > > The "nfsstat -m" for this mountpoint looks like this: > > > > nfsv4,minorversion=3D2,oneopenown,tcp,resvport,nconnect=3D1,hard,cto,no= lockd,sec=3Dsys,acdirmin=3D3,acdirmax=3D60,acregmin=3D5,acregmax=3D60,namet= imeo=3D60,negnametimeo=3D60,rsize=3D65536,wsize=3D65536,readdirsize=3D65536= ,readahead=3D1,wcommitsize=3D16777216,timeout=3D120,retrans=3D2147483647 > > > > with these mount flags in /etc/fstab: > > > > ro,nfsv4,minorversion=3D2,tcp,nosuid,noatime,nolockd,oneopenown > > > > Is there anything more we can do to help identify this issue? > Collect the output of: > # ps axHl > and > # procstat -kk -a Oh, and # netstat -a to see what the TCP connections are up to. rick > > What you show above is just a thread waiting for a lock on an NFS vnode. > What we need to figure out is what thread is holding the lock on that vno= de > while waiting for something else. > > rick > > > > > Thanks for any advice! > >