From owner-freebsd-fs@FreeBSD.ORG Fri Feb 28 19:43:34 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB7E02AD; Fri, 28 Feb 2014 19:43:34 +0000 (UTC) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77DE01060; Fri, 28 Feb 2014 19:43:34 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id kx10so1174857pab.35 for ; Fri, 28 Feb 2014 11:43:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oqznw/xViQg4dMUegOnYhCLZQoHOBTE1K8Kbxhhgvzs=; b=aLCfxnU8NBay5v65Q6uokZab2TS1RsW/8XsWnJ6jx2aaOqwJg2yyVZ/zUxRfb6cW9Z ovjohhhnc1oC8DZykIQJodRarlEibbdHMqdMS0cOiXEaZZwQA/pQwFDzk05tthCdQv/a v+PRh16ecuCauhGtFKHZwBMzB3FjdOFPGMVonb7l3wr/OYHcV6s2PahOqLElDYh4rdNW f+D0+XAoJMUGx0PObFvWuC4pc53MWojyqwbNOxNNsMQ6hDA5pRN/VinM3BKgcb1vAu4R xrkykvnOA6zgS7tCt2Y+PeveaFybfC/YfXqhnvOPU0vIj9JnF0zL/G8fBLOBGqoRc6Ix tHdA== MIME-Version: 1.0 X-Received: by 10.66.163.138 with SMTP id yi10mr5428527pab.95.1393616614073; Fri, 28 Feb 2014 11:43:34 -0800 (PST) Received: by 10.70.55.7 with HTTP; Fri, 28 Feb 2014 11:43:34 -0800 (PST) In-Reply-To: <1393616123.28153.89089441.54713282@webmail.messagingengine.com> References: <530F6475.4090508@gmail.com> <1393616123.28153.89089441.54713282@webmail.messagingengine.com> Date: Fri, 28 Feb 2014 13:43:34 -0600 Message-ID: Subject: Re: ZFS and Wired memory, again From: Adam Vande More To: Mark Felder Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 19:43:34 -0000 On Fri, Feb 28, 2014 at 1:35 PM, Mark Felder wrote: > > > > > > > Without question, cron could do it. > > > > I can't see cron using kernel memory; that just doesn't make sense to > me. Not even the periodic scripts that cron executes should be able to > balloon kernel like that. > > I think I know what meant to infer though -- that some nonstandard cron > script is doing something ugly. He's running 150 TB on 3 GB of mem. Periodic I think could consume that alone. -- Adam