Date: Fri, 30 Sep 2022 11:52:50 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 266236] ZFS NFS : .zfs/snapshot : Stale file handle Message-ID: <bug-266236-3630-ayi6A1SaAX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266236-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-266236-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=3D266236 florian.millet@laposte.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |florian.millet@laposte.net --- Comment #8 from florian.millet@laposte.net --- We are hit by this problem as well. I would add that the version of NFS used by the client has no impact, NFSv3= or NFSv4 has the problem. When FreeBSD changed from ZoF to OpenZFS 2.x in 13, there does seem to be a change in the unmounting of the .zfs directory (see https://cgit.freebsd.org/src/tree/sys/contrib/openzfs/module/os/freebsd/zfs= /zfs_ctldir.c?h=3Dreleng/13.1 vs https://cgit.freebsd.org/src/tree/sys/cddl/contrib/opensolaris/uts/common/f= s/zfs/zfs_ctldir.c?h=3Dreleng/12.3) a new function zfsctl_snapshot_unmount has been added in OpenZFS 2.x, and if you compare it to the old zfsctl_umount_snapshot, the logic is quite differ= ent. Perhaps we have a regression here ? --=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-266236-3630-ayi6A1SaAX>