Date: Wed, 22 Aug 2012 17:35:29 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: RW <rwmaillists@googlemail.com> Cc: freebsd-questions@freebsd.org Subject: Re: /tmp filesystem full Message-ID: <CAHu1Y71Y_cxv_qgQaMmzdx5kZHtXGuLGaxx9QQAE8QBWGL3fUA@mail.gmail.com> In-Reply-To: <20120822232907.34fc82fc@gumby.homeunix.com> References: <201208221934.q7MJYfwM063804@mail.r-bonomi.com> <1345664911.2501.8.camel@z6000.lenzicasa> <CAHu1Y72xwNevgKQ8eVYYOzGC80-511DtDe8kJMWbYJm5Tq28CA@mail.gmail.com> <20120822232112.07ac3517@gumby.homeunix.com> <20120822232907.34fc82fc@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 22, 2012 at 3:29 PM, RW <rwmaillists@googlemail.com> wrote: > Sorry I misread the previous post which *was* referring to an md device, > but the rest is right. Not really. ;-) The one compelling reason to use an md filesystem for /tmp or /var is when you have no swap, and/or your root fs is read only (or read mostly), as with embedded computers, Soekris boxes booting from CF, USB stick, or even mSATA (I wouldn't swap on a partition on an MLC mSATA device). In that case, you most certainly want to reserve the space for the filesystem at creation time. Usually /tmp -> /var/tmp is that case. - M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y71Y_cxv_qgQaMmzdx5kZHtXGuLGaxx9QQAE8QBWGL3fUA>