Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Oct 2011 13:29:18 +0200
From:      Attila Nagy <bra@fsn.hu>
To:        Jeremy Chadwick <freebsd@jdc.parodius.com>
Cc:        freebsd-fs@freebsd.org, delphij@freebsd.org, Adrian Chadd <adrian@freebsd.org>
Subject:   Re: is TMPFS still highly experimental?
Message-ID:  <4E899C8E.7040305@fsn.hu>
In-Reply-To: <20111002020231.GA70864@icarus.home.lan>
References:  <CAOfDtXMm9K_fbOmvG2gvXxDfKakkgpPt9MLifqDxa4wCibMExg@mail.gmail.com> <alpine.GSO.1.10.1110011122030.882@multics.mit.edu> <CADLo83-s_3H8PbbxOPPxbe0m10U0U5JW-feB294dFs%2BQ3iTWvg@mail.gmail.com> <CAGMYy3ssi%2BkAuufDTHA1z6u7jRrZwRRkCCkcO94GHNGF9Rku_w@mail.gmail.com> <20111002020231.GA70864@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On 10/02/11 04:02, Jeremy Chadwick wrote:
> On Sat, Oct 01, 2011 at 06:02:39PM -0700, Xin LI wrote:
>> On Sat, Oct 1, 2011 at 8:48 AM, Chris Rees<crees@freebsd.org>  wrote:
>>> I've also not heard of anyone using it with zfs successfully- it tends to
>>> shrink rapidly.
>> I'm quite surprised with this assertion.  I use tmpfs on my own system
>> and I never see such problem as long as one have sufficient swap
>> space.
>>
>> Not to say there is no problem --there is no way to say "commit this
>> amount of memory to ZFS" but really I have never hit this exact
>> alleged problem...
> Its been reported multiple times by multiple people, and there has been
> no official word on -fs, -stable, or zfs-devel that this specific
> problem has been fixed:
>
> * miyamoto moesasji
>    - 2011/01/01
>    - 8.2-PRERELEASE (thus RELENG_8)
>    - World/kernel build date unknown
>    - http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/060850.html
>    - http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/060852.html
>    - http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/060860.html
>    - http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/060861.html
>    - Statement from Ivan Voras that it's a known problem:
>    - http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/060867.html
>
> * Atilla Nagy
>    - 2011/01/19
>    - 8.2-PRERELEASE (thus RELENG_8)
>    - World/kernel build date of 2011/01/08
>    - http://lists.freebsd.org/pipermail/freebsd-fs/2011-January/010496.html
>    - http://lists.freebsd.org/pipermail/freebsd-fs/2011-January/010497.html
>    - http://lists.freebsd.org/pipermail/freebsd-fs/2011-January/010498.html
>    - http://lists.freebsd.org/pipermail/freebsd-fs/2011-January/010499.html
>    - http://lists.freebsd.org/pipermail/freebsd-fs/2011-January/010501.html
>    - http://lists.freebsd.org/pipermail/freebsd-fs/2011-January/010569.html
>    - Ivan Voras mentions a thread he started on -CURRENT circa 2010/11/21
>      about this problem:
>      http://www.mail-archive.com/freebsd-current@freebsd.org/msg126491.html
>
For me, the bug is still here:
$ uname -a
FreeBSD b 8.2-STABLE FreeBSD 8.2-STABLE #5: Wed Sep 14 15:01:25 CEST 
2011     root@buildervm:/data/usr/obj/data/usr/src/sys/BOOTCLNT  amd64
$ df -h /tmp
Filesystem    Size    Used   Avail Capacity  Mounted on
tmpfs           0B      0B      0B   100%    /tmp

I have no swap configured. The machine has 64 GB RAM.
vm.kmem_size=60G; vfs.zfs.arc_max=55G; vfs.zfs.arc_min=20G



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E899C8E.7040305>