Date: Sat, 13 Jan 2024 21:38:51 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: FreeBSD User <freebsd@walstatt-de.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: NFSv4 crash of CURRENT Message-ID: <1369645989.13766.1705178331205@localhost> In-Reply-To: <20240113193324.3fd54295@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_13765_1602708230.1705178331199 Content-Type: text/plain; charset=us-ascii; format=flowed 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 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body><br><p><small><strong>Van:</strong> FreeBSD User <freebsd@walstatt-de.de><br><strong>Datum:</strong> 13 januari 2024 19:34<br><strong>Aan:</strong> FreeBSD CURRENT <freebsd-current@freebsd.org><br><strong>Onderwerp:</strong> NFSv4 crash of CURRENT<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P --> <!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->Hello,<br> <br> running CURRENT client (FreeBSD 15.0-CURRENT #4 main-n267556-69748e62e82a: Sat Jan 13 18:08:32<br> CET 2024 amd64). One NFSv4 server is same OS revision as the mentioned client, other is FreeBSD<br> 13.2-RELEASE-p8. Both offer NFSv4 filesystems, non-kerberized.<br> <br> I can crash the client reproducable by accessing the one or other NFSv4 FS (a simple ls -la).<br> The NFSv4 FS is backed by ZFS (if this matters). I do not have physicla access to the client<br> host, luckily the box recovers.<br> <br> I have no idea what causes this problem ...<br> <br> Kind regards,<br> <br> O. Hartmann<br> <br> <br> -- <br> O. Hartmann<br> <br> </div><!-- TextPlainViewer --> <hr> </div><!-- MessageRFC822Viewer --> </blockquote><br><br>Do you have something like a panic message, stack trace or core dump?<div><br></div><div>Regards</div><div>Ronald</div></body></html> ------=_Part_13765_1602708230.1705178331199--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1369645989.13766.1705178331205>