Date: Sat, 13 Jan 2024 19:41:30 -0800 From: Rick Macklem <rick.macklem@gmail.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: FreeBSD User <freebsd@walstatt-de.de>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: NFSv4 crash of CURRENT Message-ID: <CAM5tNy5aat8vUn2fsX9jV=D9yGZdnO20Q0Ea7qtszx%2BzSES2bw@mail.gmail.com> In-Reply-To: <1369645989.13766.1705178331205@localhost> References: <20240113193324.3fd54295@thor.intern.walstatt.dynvpn.de> <1369645989.13766.1705178331205@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ronald Klop <ronald-lists@klop.ws>= wrote: > > > 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 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy5aat8vUn2fsX9jV=D9yGZdnO20Q0Ea7qtszx%2BzSES2bw>