From nobody Sun Dec 24 15:24:52 2023 X-Original-To: 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 4SylFw2KXHz54lQc for ; Sun, 24 Dec 2023 15:24:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SylFw0kHdz4MSk for ; Sun, 24 Dec 2023 15:24:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1703431492; a=rsa-sha256; cv=none; b=a2v8mg3qDDH0JvbksJ32N/55/KNFB8vH93nLIh+wDRHXlHWth+PVBU+YHQNbumh3wV/go1 FJS30bPVqvCLQSONzhx/f5JAbuTIDUjUaG5gv2gvHouNFY0y44OR4xRTqGCCDFVKOWOYEV Cp49r2FON1NfOqLiJlq/Q+M/rbadgR6rZ/ED774eGzpqiIeHYqFUfmMa6oADDpVVTeY2RB UqU00a67iuXjD/u0AxZMJxnbAACeB86lPxiHMuE46q5siIvuP15UyR+rhS+iJsE4shBp0w OkO22XxC3Mza/Xuba+p5spLV6eHhu8TwxlYI7cerLD7sDnAbreyJFtvC+5aYqA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1703431492; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=S+VZobrxXqNK6mfcVfF2yrh7048NnP3VtNqKTBvsoBM=; b=bl9KwWZ7+WxSuTlsRb0uOXsmIUvbdBvi0dJ4MCxtyh6kZ5fA2D4dFHIxHk3sKkloLPOVgM 5jk/37Bxwuycb2Kq0wCNbfD7kAWe9wA0Dd3J2VhRs3UfCEN4vDW9b3zHKrTqcuoBcZycNU 4E6jrogj/8M9Mhkt8XKlXB6isJmAW9gjF1fOQP6b7lsgGSXaibhxNipo9Ha5JIp5ypKMrt +ZL9mZ9WjNTVygMrg/Hz9mciIoQOJUvGpZmSebxc2tkcoy57aX8VDXCOqf48Lf7g8U+xwA E1W7EwHG177WdQjharvW2THrkyoHRc2DgDOfnPTNeUBmYAPlQAo84B9JVI+05w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4SylFv6w8szYrw for ; Sun, 24 Dec 2023 15:24:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3BOFOpue066207 for ; Sun, 24 Dec 2023 15:24:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3BOFOp4B066206 for fs@FreeBSD.org; Sun, 24 Dec 2023 15:24:51 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 275905] nfs client: mount becomes unresponsive Date: Sun, 24 Dec 2023 15:24:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275905 Rick Macklem changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@FreeBSD.org --- Comment #2 from Rick Macklem --- You haven't used the "intr" and/or "soft" mount options by any chance? These are guaranteed to break NFSv4 mounts. The renewthread is stuck in nfsv4_sequencelookup() because there are no session slots available. - This can happen for "soft" or "intr" mounts because the RPC reply does not get processed properly to release the session slot. - If the mount does not use "soft" nor "intr", then there is some other reason that the replies are not being processed. --> I'll think about this. It might be a side effect of a RPCSEC_GSS session being expired so the client cannot de-encrypt the RPC reply, or something like that. Typically, the RPCSEC_GSS session (not the same thing as a NFSv4 session, just to make the terminology confusing) expires when the TGT used to acquire it expires. It will be re-created upon the next RPC if there is a valid TGT, but that might be too late for processing of an RPC reply. (With sec=3Dkrb5p the reply is encrypted, so it cannot be processed without a valid RPCSEC_GSS session. Once all session slots are in use and no RPC reply is processed to release one, the mount is hung and the only fix is to "umount -N " or reboot the client machine. --=20 You are receiving this mail because: You are the assignee for the bug.=