Date: Wed, 14 Jul 2021 23:10:44 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 257187] NFSv3 server creates symlinks that local clients can't read [ZFS] Message-ID: <bug-257187-3630-gjzNJbWnPm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257187-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-257187-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257187 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asomers@FreeBSD.org --- Comment #1 from Alan Somers <asomers@FreeBSD.org> --- Firstly, does that symlink cross a mountpoint? It may be that the target exists as seen from the NFS client, but not on the server. Assuming that isn't the problem, dtrace is your friend. Try something like this: sudo dtrace -i 'sdt:zfs::set-error /arg0 =3D=3D 2/ {stack();}' -c "readlink /foo/bar/baz" If the error is coming from ZFS, you should find out where. But if it isn't coming from ZFS, then run this instead: sudo dtrace -i 'fbt:kernel::return /arg1 =3D=3D 2 && pid =3D=3D $target/ {t= race(".");}' -c "readlink /foo/bar/baz" That command will have plenty of false positives, so don't print the stack traces just yet. If you spy a function that looks likely, then suitably mo= dify your D script and prints its stack trace. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257187-3630-gjzNJbWnPm>