From owner-freebsd-fs@FreeBSD.ORG Fri Feb 28 19:48:23 2014 Return-Path: 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 BF456524; Fri, 28 Feb 2014 19:48:23 +0000 (UTC) Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 66A5410B4; Fri, 28 Feb 2014 19:48:23 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id jz11so1219764veb.39 for ; Fri, 28 Feb 2014 11:48:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2cWNiMfaUWrWBIxfsPcgoM4nwJBa1zjIJHqZj1HWTyA=; b=Qmr/wULNDfPktRYk22jIdev09d9kWdOhN885bc0IYIb5YXL5R0yFKMGkn9GsmuJD1c 3agQRLCHIQWFyR+k3KPAHdzHUaNhQ9d90bo6nVwzXWFxRaSsQruUYpOERjvDLEtrbNrp m2a+UWjVNITCIOK8lMSGvx9Ey7HUqkiZ+N3lGV9/gvWyjTxaz3ZWYvS2KzfJRrA/5H/M B/uNHYlX4nbRzck0/1YnFKdOE8iyAhOMomp/SfqAeulq2LfkhOuP9TfgD7Lp3MKEKwWv M724P/pt9G+e4JqMJk6FOmgBWpbf7Nt1OjOQZ/+3bANP+6IItw/0GeFMYgICoz66rRO8 8smQ== X-Received: by 10.220.98.204 with SMTP id r12mr93857vcn.48.1393616902467; Fri, 28 Feb 2014 11:48:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.91.74 with HTTP; Fri, 28 Feb 2014 11:48:02 -0800 (PST) In-Reply-To: References: <530F6475.4090508@gmail.com> <1393616123.28153.89089441.54713282@webmail.messagingengine.com> From: Anton Sayetsky Date: Fri, 28 Feb 2014 21:48:02 +0200 Message-ID: Subject: Re: ZFS and Wired memory, again To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 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:48:23 -0000 2014-02-28 21:43 GMT+02:00 Adam Vande More : > 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. And again - read _carefully_. System with 3G RAM is only test system with single disk.