Date: Fri, 21 Aug 2020 08:35:31 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 248804] sysutils/zfstools: Doesn't clean up old snapshots that were in use Message-ID: <bug-248804-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248804 Bug ID: 248804 Summary: sysutils/zfstools: Doesn't clean up old snapshots that were in use Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: bdrewery@FreeBSD.org Reporter: danmcgrath.ca@gmail.com Flags: maintainer-feedback?(bdrewery@FreeBSD.org) Assignee: bdrewery@FreeBSD.org Hi, This is a bit of an old bug that I've been dealing with for quite some time, and I am not 100% sure on the cause, but have some theories. I am using zfstools 0.3.6_1. This bug is that old snapshots that were locked from delete (in use) during backups, I presume, prevent the script from cleanup up the snapshot. The problem is that the system never goes back to all of the past ones that it missed to clean them up. The result is that you are left with a bunch of snapshots laying around from years ago, in some cases, for something like an hourly snapshot. eg: data/ezjail/my.jail.name.org@zfs-auto-snap_hourly-2019-08-02-08h00 IMHO, this tool should be considered to "own" the entire namespace of "zfs-auto-snap_$timestamp" etc, and thus no harm in going over the entire history to at least clean up older stuff that sticks around an extra moment. Any ideas if this is a bug or something that can be considered implementing= ? I know it wouldn't be the first time that our systems ran low on space due to this issue. Thanks! --=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-248804-7788>