From owner-freebsd-stable@FreeBSD.ORG Mon May 31 00:55:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26619106566C for ; Mon, 31 May 2010 00:55:46 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id F05C98FC12 for ; Mon, 31 May 2010 00:55:45 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1OItI8-0005FV-13; Sun, 30 May 2010 20:55:44 -0400 Date: Sun, 30 May 2010 20:55:43 -0400 From: Gary Palmer To: David Magda Message-ID: <20100531005543.GA77116@in-addr.com> References: <4C017419.9010909@strauser.com> <4632C12D-2B1E-4073-B2C9-E9D15C212EF1@ee.ryerson.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4632C12D-2B1E-4073-B2C9-E9D15C212EF1@ee.ryerson.ca> Cc: FreeBSD-STABLE Mailing List Subject: Re: Make ZFS auto-destroy snapshots when the out of space? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2010 00:55:46 -0000 On Sun, May 30, 2010 at 08:33:40PM -0400, David Magda wrote: > On May 29, 2010, at 16:07, Kirk Strauser wrote: > > >I'd propose standardizing on an attribute like > >org.freebsd:allowautodestroy. Modify ZFS's disk full behavior [...] > >Also run a daily periodic script to ensure that the free space stays > >below a configurable threshold each day so that ZFS isn't constantly > >butting up against completely full drives. > > > Why not simply have a script that runs and checks for pool usage and > then deletes snapshots with that attribute if necessary? Why do you > need to have have it built into ZFS? Suggestion: zfs can have settings that trigger an event to be delivered to devd when a filesystem hits a certain percentage full (or under a certain percentage free space left). That way you can have the event triggered at the filesystem level, which I believe is the correct thing to do (so you're not polling), and also delivers the level of control you want. Regards, Gary