Date: Mon, 10 Jan 2011 23:14:24 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@spoerlein.net> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org, avg@freebsd.org Subject: Re: tmpfs regression in recent -STABLE Message-ID: <20110110221424.GK23329@acme.spoerlein.net> In-Reply-To: <201101101649.14385.jhb@freebsd.org> References: <20110110214004.GI23329@acme.spoerlein.net> <201101101649.14385.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10.01.2011 at 16:49:14 -0500, John Baldwin wrote: > On Monday, January 10, 2011 4:40:04 pm Ulrich Spörlein wrote: > > Hey, > > > > the following line in fstab used to work just fine for my /tmp: > > > > tmpfs /tmp tmpfs rw,size=1g,mode=1777 0 0 > > I thought there was a thread recently about tmpfs not supporting things like > "1g" for size? Nah, this must be some leak of another kind. Luckily I could bandaid this by unionfs mounting an mfs disk over /tmp so programs continue to run. But, tmpfs really is out of resources, as I cannot create new tmpfs's for example: root@elmar: ~# mount -t tmpfs tmpfs /media mount: tmpfs : No space left on device And besides, the /tmp mount comes up fine and shows enough free space (I checked this the last time, after I had rebooted the box). Cheers, Uli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110110221424.GK23329>