From nobody Sat Jan 13 20:38:51 2024 X-Original-To: freebsd-current@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 4TC9H763sTz56cHC for ; Sat, 13 Jan 2024 20:38:59 +0000 (UTC) (envelope-from SRS0=cu6x=IX=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4TC9H747nBz4KfS for ; Sat, 13 Jan 2024 20:38:59 +0000 (UTC) (envelope-from SRS0=cu6x=IX=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sat, 13 Jan 2024 21:38:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1705178331; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=2ckE3eHZirzyuocojfxNsMKB6pZrj0EUTAq8SqyiGC4=; b=fYwTl15EUx0afsSyWPusGzWYQNzG2Lgt7ptQsx700X9HWn7fqq+pI9Qel5Psu1Ra/8Sy6n QQrHvNosBSGV6DXAgvzCQ2DR15fJXV+I/kN8Znp+FNu21JphQoBRZCV88QhFrLG0TSrnOh fWEbfm8tLOlr0FVcttdBNCQ8lFw+6ph8gfRUE/zjaZ0iWo3UBO+qDhV8S2FKEQAZ2d7yh1 /cZNnu3SBjxlz80/SY97faSLhN4oTaSsBnihPU/G/6z187FAcYFaoEUq2aRvnYvZ8w5C8T sjzKtccgoHTMjkTao7p62a+Wg7+mrKMmYaPLFpdWZGft/uUoN5GlbI93HLLWAw== From: Ronald Klop To: FreeBSD User Cc: FreeBSD CURRENT Message-ID: <1369645989.13766.1705178331205@localhost> In-Reply-To: <20240113193324.3fd54295@thor.intern.walstatt.dynvpn.de> Subject: Re: NFSv4 crash of CURRENT List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13765_1602708230.1705178331199" X-Mailer: Realworks (685.3) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4TC9H747nBz4KfS X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] ------=_Part_13765_1602708230.1705178331199 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: FreeBSD User Datum: 13 januari 2024 19:34 Aan: FreeBSD CURRENT Onderwerp: NFSv4 crash of CURRENT > > > Hello, > > running CURRENT client (FreeBSD 15.0-CURRENT #4 main-n267556-69748e62e82a: Sat Jan 13 18:08:32 > CET 2024 amd64). One NFSv4 server is same OS revision as the mentioned client, other is FreeBSD > 13.2-RELEASE-p8. Both offer NFSv4 filesystems, non-kerberized. > > I can crash the client reproducable by accessing the one or other NFSv4 FS (a simple ls -la). > The NFSv4 FS is backed by ZFS (if this matters). I do not have physicla access to the client > host, luckily the box recovers. > > I have no idea what causes this problem ... > > Kind regards, > > O. Hartmann > > > -- > O. Hartmann > > > > > Do you have something like a panic message, stack trace or core dump? Regards Ronald ------=_Part_13765_1602708230.1705178331199 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: FreeBSD User <freebsd@walstatt-de.de>
Datum: 13 januari 2024 19:34
Aan: FreeBSD CURRENT <freebsd-current@freebsd.org>
Onderwerp: NFSv4 crash of CURRENT

Hello,

running CURRENT client (FreeBSD 15.0-CURRENT #4 main-n267556-69748e62e82a: Sat Jan 13 18:08:32
CET 2024 amd64). One NFSv4 server is same OS revision as the mentioned client, other is FreeBSD
13.2-RELEASE-p8. Both offer NFSv4 filesystems, non-kerberized.

I can crash the client reproducable by accessing the one or other NFSv4 FS (a simple ls -la).
The NFSv4 FS is backed by ZFS (if this matters). I do not have physicla access to the client
host, luckily the box recovers.

I have no idea what causes this problem ...

Kind regards,

O. Hartmann

--
O. Hartmann

Do you have something like a panic message, stack trace or core dump?

Regards

Ronald

------=_Part_13765_1602708230.1705178331199--