From nobody Sun Jan 14 03:41:30 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 4TCLg45sd0z56w59 for ; Sun, 14 Jan 2024 03:41:52 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TCLg357wdz4698 for ; Sun, 14 Jan 2024 03:41:51 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ot1-x336.google.com with SMTP id 46e09a7af769-6ddec7e5747so3146268a34.3 for ; Sat, 13 Jan 2024 19:41:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705203710; x=1705808510; 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=aTAomrFqusdSwi2z0jmQ9WQXfAngHzHGLUf9rgwxhlU=; b=QKi8Y2Ezs/oIzdWk006YMygByPfgIJIsV3RF7Kej90l4XWyh+flQIQE0K+qT5VlAVz 8VH8N/3e2rOZQUEYHJb9QJyY5m/4rGSLQRLF6hJ/Dvx58nKyrFS2SQVnfVyiwXCLxTK9 Ax1nkPAaAa0IwTg+TMXcrQgEu8kg3H9GJLuVIxzzNtWNBsXiS/66LOZaxE1f/F10+sZD wEnPxpKVDsfEl3H/o9eu/VBqZlYzZ4MnCJmScj1NwEesCU5QTid1L9PsS5tt1CRhUVJ/ Xj/Xky9hZvSjqzZ0a7EyRbyiZrtXLLQY314mUPUw37xMAqiJH/SgqCaQ5sqr8EawvNfG Q8jQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705203710; x=1705808510; 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=aTAomrFqusdSwi2z0jmQ9WQXfAngHzHGLUf9rgwxhlU=; b=MwzCzFVMy8VBdjBXBg8HKtyi54YH9KgI2lV6JvKKvdCCZTwym2XmK3OKcLEi26/Rqw r63PiJeyjhYYYpvAv4eatY7kffQSKLesIn8i1q/Dy4mc/hYyTQkglBcKLr6MHLkK2GUa DByO33t5oRMfJGRttuykQBypHVza9JohO+gFlNIibFZLpshBkAoORgXSoPWA82SRpqQX 2xfR/k6URNSBYyvBbfJL6QdmL+Tu0kPPF8VT3nmddKiLFF6sRPuFhi/iqEzaphyq0iOz h5CpiTuj7S6+ojtwIb0hF4CtgsIcVx4Mvt6lCuiSuLs/MoNumYiSRLnj5CkdiKM6TycO DoOQ== X-Gm-Message-State: AOJu0YzHwqjO6+IlxTgJgO2RiRIGvsJ9/h8arOGJZujx2VQFkxIpmxU3 4zJFCt9GqWqmQsHyYUO8XE3GVHnfK18/QjyRf/HsJrQ= X-Google-Smtp-Source: AGHT+IFlrH77eACurUiz8zn59RWEIu6TC1MNKNP19OAXE9i3i53Ar57BZkdZNnIkN5YZY2/ZDyxDe69ST0EPGTImzCo= X-Received: by 2002:a05:6808:2393:b0:3bd:60d4:5466 with SMTP id bp19-20020a056808239300b003bd60d45466mr4306150oib.36.1705203709989; Sat, 13 Jan 2024 19:41:49 -0800 (PST) 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 References: <20240113193324.3fd54295@thor.intern.walstatt.dynvpn.de> <1369645989.13766.1705178331205@localhost> In-Reply-To: <1369645989.13766.1705178331205@localhost> From: Rick Macklem Date: Sat, 13 Jan 2024 19:41:30 -0800 Message-ID: Subject: Re: NFSv4 crash of CURRENT To: Ronald Klop Cc: FreeBSD User , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4TCLg357wdz4698 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)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ronald Klop = wrote: > > > 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 cl= ient, 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 F= S (a simple ls -la). > The NFSv4 FS is backed by ZFS (if this matters). I do not have physicla a= ccess to the client > host, luckily the box recovers. Did you rebuild both the nfscommon and nfscl modules from the same sources? I did a commit to main that changes the interface between these two modules and did bump the __FreeBSD_version to 1500010, which should cause both to be rebuilt. (If you have "options NFSCL" in your kernel config, both should have been rebuilt as a part of the kernel build.) rick > > 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