Date: Mon, 16 May 2016 15:38:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 209093] ZFS snapshot rename : .zfs/snapshot messes up Message-ID: <bug-209093-3630-VivHvkX3pR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209093-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-209093-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=3D209093 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Mon May 16 15:37:41 UTC 2016 New revision: 299949 URL: https://svnweb.freebsd.org/changeset/base/299949 Log: try to recycle "snap" vnodes as soon as possible Those vnodes should not linger. "Stale" nodes may get out of synchronization with actual snapshots. For example if we destroy a snapshot and create a new one with the same name. Or when we rename a snapshot. While there fix the argument type for zfsctl_snapshot_reclaim(). Also, its original argument can be passed to gfs_vop_reclaim() directly. Bug 209093 could be related although I have not specifically verified that. Referencing just in case. PR: 209093 MFC after: 5 weeks Changes: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ctldir.c --=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-209093-3630-VivHvkX3pR>