From owner-freebsd-fs@FreeBSD.ORG  Fri Feb 28 19:58:13 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 22268A2F
 for <freebsd-fs@freebsd.org>; Fri, 28 Feb 2014 19:58:13 +0000 (UTC)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id E0E0911A2
 for <freebsd-fs@freebsd.org>; Fri, 28 Feb 2014 19:58:12 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 862C021222;
 Fri, 28 Feb 2014 14:58:09 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute4.internal (MEProxy); Fri, 28 Feb 2014 14:58:09 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:cc:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=cXWe5LugXI6XBBVKwohn7jN3QSg=; b=pki
 NRRfffrzn1U5gnI6nW/u561dqVRccR/ZVCDuo/6yjr8k6EuPsp4jP68fHAjqbMBs
 Xz2C35CzLZ1KrgW6dqx0RQPnEOqtYGZkXk3WNlGq8ZXzmPHMqIt9BmpVy+NrFWBj
 i6twWVb7W1jM5jKpaQ84vspB7/uc9DV2ox01aAFg=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id D998C112A0D; Fri, 28 Feb 2014 14:58:08 -0500 (EST)
Message-Id: <1393617488.2929.89095301.157E5E1B@webmail.messagingengine.com>
X-Sasl-Enc: DoPuTycToYhF48tOSvegiDQ1Q+otz9AQb+NLhTvwPH98 1393617488
From: Mark Felder <feld@FreeBSD.org>
To: Adam Vande More <amvandemore@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-4527a23f
In-Reply-To: <CA+tpaK246eKwjvPXgzcxt_e5+=udietjPQKSdDV+iLRG-T2RDQ@mail.gmail.com>
References: <CAFG2KC+ZSHEVFbpPD9e1QHRdY=Sd6EuAD80vyDLDDQcpgCQNhA@mail.gmail.com>
 <530F6475.4090508@gmail.com>
 <CA+D9QhtVkYNoEGwhx-EJi9X1jr_UN2rgYxbZtA99qcT4UA-8kA@mail.gmail.com>
 <CAFG2KCLSSBwR5JbLdnVPy6E8UeGiWWCGsFcEjeU+eU5F2Xm+Sw@mail.gmail.com>
 <f6dfa6229d7707dd5657fae427f79ba2@webmail.lerctr.org>
 <CAFG2KCLeaucA=3aJ+_NzsfzOfVNXtiCnrRWwCMhW==-JT7wkCA@mail.gmail.com>
 <CA+tpaK3aQ60CrrVksb69muUXGhTD5Vtn+pu6G7g=4E9eCLC_OQ@mail.gmail.com>
 <1393616123.28153.89089441.54713282@webmail.messagingengine.com>
 <CA+tpaK246eKwjvPXgzcxt_e5+=udietjPQKSdDV+iLRG-T2RDQ@mail.gmail.com>
Subject: Re: ZFS and Wired memory, again
Date: Fri, 28 Feb 2014 13:58:08 -0600
Cc: freebsd-fs <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 19:58:13 -0000



On Fri, Feb 28, 2014, at 13:43, Adam Vande More wrote:
> On Fri, Feb 28, 2014 at 1:35 PM, Mark Felder <feld@freebsd.org> 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.
> 

Which periodic script are you referring to? The daily security check? I
suppose I could see resource usage increase after checking for new
setuid bits... assuming he had a lot of files to crawl through. But I
don't actually know if that would do much to wired memory.