From nobody Fri May 31 20:11:20 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 4VrZ5J71Gvz5LJGW for ; Fri, 31 May 2024 20:11:32 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 4VrZ5J2QLqz4Rwf for ; Fri, 31 May 2024 20:11:32 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=UdCO7XoF; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2607:f8b0:4864:20::531 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com Received: by mail-pg1-x531.google.com with SMTP id 41be03b00d2f7-6c702226b0aso203722a12.1 for ; Fri, 31 May 2024 13:11:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717186291; x=1717791091; 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=rVJsNG2y9MiYAXqao7yD74ScjdqXl7f0RY1IaJ57rNQ=; b=UdCO7XoFI6ZBzgSVytjw0pX5OsiwoIs0jyPCC0m3FeMqDa8J9eFLNNtqgdyQKhlUpg q9UdaN+1ZQcHbt0rMZWEu+U3ADcKPDTXEA6QjvRq4aIeCCrF/UqyKeKPZuYmGBt0NvzC UvA7bSS6svQ8Bi+x8nehVi0jfRDKKkhQ6Ob/c98g6Z7q3x/GCJ0jynKdP8UmGVAd5Iba YtFt6M8WkGzqFsTeWiJU33CfI1P7Qw/7MugvfsjBtEH8NBRSK971hLEEUo3uSDF0aL08 gJgyEQCR0ko7Hxeu8vf4X2KSzS516IXy39eVsvF94r63Khx+6rIAbxUXjT1T1WrnXueB bpTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717186291; x=1717791091; 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=rVJsNG2y9MiYAXqao7yD74ScjdqXl7f0RY1IaJ57rNQ=; b=efbodtzuLTIwdWQZx78YFeuFduhv650NuLjPTy1sraUgiqA/23Rg3/XSIECi97ef07 R4qpFbcX7RiVLkWihFSEYWobguEur8X7tiT8y/meJYw5LmW+ofCkhNiNcAgZL8bghFc+ LM3uNa5o09iTacjYJQW8tTKg6nKR7bS5sPqX0XCfEV/I8cvk+2AnZiuB+MAkVZutDs4a kg/eK8yGPk4N5uApYrl36J0pl0jiNA/7kAo3dnTFSFkdYREfngoG+SlHxypfTQI/weMt rT/sQ9aFzojs8+QRvaOpu+ltbAhDQIuyCQBr76frUSw93r8WwBDNrnPtIcaoNHhLRdIi GnlQ== X-Gm-Message-State: AOJu0YxZ9iWoLEXJchRzOM1K/StcsTAE/OC7s8zKNq2sw7sEZKE9rFL8 ct+gzIiZscNvN2G8LlPFlq3g4vnJiJ/8oUHXLqqeuh1ARP5unHtKrz3IgsA9nNZq2FzqSUrnsiq iT+ceX0PWDfyC6zyKwfZkxm+UFEL0 X-Google-Smtp-Source: AGHT+IH4G+3Bu+INPC54DveA5bmcnrJ9/bsFRZJJLyAbx7BAMf8/Yck6SX3/PppnREkIMF+Tn2TMEgH+hU0bXyzqYgc= X-Received: by 2002:a17:90a:c7cf:b0:2b0:e497:56f2 with SMTP id 98e67ed59e1d1-2c1c43ee4c1mr4354323a91.10.1717186290769; Fri, 31 May 2024 13:11:30 -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 13:11:20 -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.72 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.72)[-0.722]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_ALL(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::531:from] X-Rspamd-Queue-Id: 4VrZ5J2QLqz4Rwf 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 machin= es. > > 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,nolo= ckd,sec=3Dsys,acdirmin=3D3,acdirmax=3D60,acregmin=3D5,acregmax=3D60,nametim= eo=3D60,negnametimeo=3D60,rsize=3D65536,wsize=3D65536,readdirsize=3D65536,r= eadahead=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 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 vnode while waiting for something else. rick > > Thanks for any advice! >