From nobody Thu Jan 27 23:12:51 2022 X-Original-To: bugs@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 7DE30197C185 for ; Thu, 27 Jan 2022 23:12:51 +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 4JlGb71Pxwz4WZZ for ; Thu, 27 Jan 2022 23:12:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 124A31F6C3 for ; Thu, 27 Jan 2022 23:12: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 20RNCpDt025049 for ; Thu, 27 Jan 2022 23:12:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 20RNCpOn025048 for bugs@FreeBSD.org; Thu, 27 Jan 2022 23:12: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: bugs@FreeBSD.org Subject: [Bug 261291] ESX NFS4.1 client hangs, server never responds to EXCHANGE_ID/CREATE_SESSION Date: Thu, 27 Jan 2022 23:12:51 +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: 13.0-STABLE 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: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643325171; 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=RJwka2a9LLmqO23oMlk2MXZbV0heoWNR2U7co0aAK0c=; b=kUQOPMkFPyo2H/dy0dKtENMckS5Hbs8w5KD1CdW1BG3Y9N/fDvVFPNDjKZIGzJwRCVBFM7 g4ER8v12+h4ZZj6IAEqFuJ4guxynD+0mOXyOCXYXYxSK4xbAq54Zkz9VXfWSpe2vrva4Lj zNXRcwANRFiNsjWe9kjAi+4ikjpaGdhxNftretz2XBAJaAm/bvo2yis2BAP2ESvwVwu3gW AubHH79eu9m7y28PQfywT1iCMJqUsCKovH4ioS5lnKmmi+/Uf90Xy9/wmvLt/YrLT5GH8i wWIcCp0r0AeRXo5DxcCsPuWjN6lDY0CFbY6AeQ6EwHOqMnyk2S/QkiVOQS3VZw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643325171; a=rsa-sha256; cv=none; b=lWlSkCQ6aoRJy9FR8YGRdsernJrU/adG+KlOfcm4zH7W74QQuwEQX0YJySud6O/xA3X1lN 5PzHIzGFYI5J6SqSi61sKluJMLMgEQIzsu6AnovYVJ5cfPwI/+pA8JJeSK3RB7vaZvb3uH +ytpjA63ys3lbl6m5gkMdQlK1mEd9rZ42Wi2EOHnBqeuSnSVAQssfEsXiAL3CzDSj2gLLY Mn5sS3n0dNsNv74+4wlL8hbPLqJTmTJOC4FsqxH87uBeGtKmthmbDOTGZcpQpfVEuwd7Lp LFgkboy5j1wW7zObCjvYaSi+hHiA6ray/MrNFDnVIt3Z7Q1GP1R+6VPZGUR3eA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261291 --- Comment #9 from Rick Macklem --- I took another look at the packet trace and I do not see any problems w.r.t. the session (sequence ops are using different slots). However, I noticed that the request it packet #644 seems to be created from 4 large TCP segment fragments. (I'm not sure what Wireshark means by TCP segment fragments, since each TCP segment is a "segment". Maybe just its way of saying the 4 TCP segments make up the two RPC requests?) Are you using jumbo frames for a net interface that will use jumbo mbuf clusters? - I think you probably already know that jumbo mbuf clusters are an accident looking for a place to happen, due to fragmentation of the mbuf cluster pool. If this is the case, try either a network interface that can do jumbo frames without using jumbo mbuf clusters or turn off the jumbo frames. The lack of a reply to the requests in packet #644 is what causes the mount to mess up and it looks like some sort of network fabric problem, possibly tickled by having a large Write and a Read lumped together in the same TCP segments? --=20 You are receiving this mail because: You are the assignee for the bug.=