From owner-freebsd-fs@FreeBSD.ORG Fri Apr 10 02:25:04 2015 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D92131A for ; Fri, 10 Apr 2015 02:25:04 +0000 (UTC) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 453B513A for ; Fri, 10 Apr 2015 02:25:04 +0000 (UTC) Received: by iebmp1 with SMTP id mp1so7371876ieb.0 for ; Thu, 09 Apr 2015 19:25:03 -0700 (PDT) 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 :content-type; bh=YesgYeyykHAN1giyf5RYLyhXV9yfvBWP+9PXFEuK4lI=; b=hC5x6N4H2kG5W0JT0TFO8NocEib2ZC3rMpAeOLCsIPUg5nU6m7cj9zCaQLEuyx+LxK 5fQ3d7tDoBU+rvxm8Z1C9iTpIwTtLBlmhm5gaAmwlCSVzH5Scg7XNvQH2GmnW660XpKr PEqLryaHDyPPHBWTmUnZhThjxENJaFCBtvgNpeIyGCFOS3EjPmjaHajI0WUQsN5jeZiP rpAcqG7r4Ghcut0yGZYZuZ3TGttuWrDm5/XL8ojXj6B6JBlT58EQdQQXgVZOlC72NE0n QkS9BIzLOD+xenD7f7yzRbY8vLg05Z8ez0HEJW5cK5Q64jsozUNH3F7uTSeJO3I7iujJ y3xQ== MIME-Version: 1.0 X-Received: by 10.107.156.19 with SMTP id f19mr51570904ioe.45.1428632703802; Thu, 09 Apr 2015 19:25:03 -0700 (PDT) Received: by 10.36.51.76 with HTTP; Thu, 9 Apr 2015 19:25:03 -0700 (PDT) In-Reply-To: References: Date: Thu, 9 Apr 2015 22:25:03 -0400 Message-ID: Subject: Re: FreeBSD/ZFS on [HEAD] chews up memory From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2015 02:25:04 -0000 > "vi some-file" and your terminal session locks up for tens of seconds > to, in some cases, more than a minute! I see this but would need to independant test whether it is more due to the FS being full or to memory condition. I really should try to test out more low physical or application memory conditions to better see any issues.