From owner-freebsd-fs@FreeBSD.ORG Mon Oct 3 22:13:43 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E22941065670; Mon, 3 Oct 2011 22:13:43 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 888828FC12; Mon, 3 Oct 2011 22:13:43 +0000 (UTC) Received: by ywp17 with SMTP id 17so4918491ywp.13 for ; Mon, 03 Oct 2011 15:13:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MYdLhI2QNR1DQPo6gPIJ1KQJAoeBA6mXE7OG0v3s4oE=; b=I7dArEJDX68ZNfA23LgIZl9/KOd1x3y/99ic8rUZA1fEQDZO7XN0ocrkcRHpVpYSoW LLkFhz8RcOBDngT8DIGHhbNTdGJUo+Zxa53xi+rieavX/QIVdTHneGXumr5fq+ETxgcs Ba0fHd79jQQbIa3i+nGlMbhfdjqGYV0rafEnU= MIME-Version: 1.0 Received: by 10.151.93.10 with SMTP id v10mr618131ybl.449.1317680022804; Mon, 03 Oct 2011 15:13:42 -0700 (PDT) Received: by 10.151.145.18 with HTTP; Mon, 3 Oct 2011 15:13:42 -0700 (PDT) In-Reply-To: References: <20111002020231.GA70864@icarus.home.lan> Date: Mon, 3 Oct 2011 15:13:42 -0700 Message-ID: From: Xin LI To: Olivier Smedts Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-fs@freebsd.org" , Ivan Voras Subject: Re: is TMPFS still highly experimental? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2011 22:13:44 -0000 On Mon, Oct 3, 2011 at 2:36 PM, Olivier Smedts wrote: [...] > Try reducing the swap size to less than the RAM size. No "configuration > issue", try with some RAM + swap that should fit all. But it's not ZFS+tmpfs specific, it can happen anywhere when memory and swap is not sufficient. Of course tmpfs and ZFS should play more well together but it's pretty much a "you get what you paid for" situation IMHO. One thing I can not yet reproduce, but sounds like a serious issue is that when system have sufficient RAM available, ZFS reports 0 in free space... If there is a test case for that then that's definitely something we need to solve sooner. Cheers, -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die