Yes, that's exactly what you need to do.
As your system already has "tmpfs" type partitions for things such as '/run'
just set up a new config for '/tmp' which is modeled on the config for '/run'.
As to the size, that will depend upon your system activity and configuration.
I'd try starting with something in the range of 20~40GB, then increase
if needed.
On Mon, 22 Dec 2014, Almond wrote:
Hi David,
so you mean to move the /tmp partition from /dev/md2 to another partition,
since /var/spool/mail and quota control are on the same partition?
and what size to reserve to the new /tmp... ?
thank you
On 22/12/2014 18:46, David B Funk wrote:
On Mon, 22 Dec 2014, Almond wrote:
hi Mark,
do you mean this?
http://fedoraproject.org/wiki/Features/tmp-on-tmpfs
but tmpfs have no quota... as you can read on that page, i'm confused...
so, that's done by default on CentOS ?
indeed, I didn't see any tmpfs on CentOS 6, as I remember...but I could be
wrong.
Do you think that if I do a "systemctl mask tmp.mount, and reboot." I
solve this issue, and then if needed the apps write on /tmp on /dev/md2
or I misunderstood the matter? So do you think that the /tmp returned by
the error is not the /tmp on /dev/md2 ?
thanks
Yes, tmpfs has no quota, that's EXACTLY what you need.
Your problem is caused because your '/tmp' directory is on the root
partition (the same one as your mail store and almost everything else)
so it's affected by the quotas you've put on your root partition to control
your users. Thus when Spamassassin/ClamAV need to create large temporary
files to get their work done they run into your quota control and fail.
Classical Unix disk partition layout would put '/tmp' and '/var' on
seperate
partitions so they could be not quota controlled and could be completely
filled by a run-away program but not bring the whole system to a crashing
halt.
Simple hobbyest systems don't bother with that complexity but can run into
this
kind of problem. Thus using "tmpfs" technology is a way to get around this
issue.
You do NOT want quota control on the temp-scratch-working storage so
programs
can get their job done with out running into quota control inducted
problems.
The meaning of 'scratch/working' storage is that it is temporary space used
to get a job done and then deleted.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
