Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Dec 2007 16:21:39 -0600
From:      Paul Schmehl <pauls@utdallas.edu>
To:        freebsd-questions@freebsd.org
Subject:   Re: /tmp: filesystem full
Message-ID:  <9D7B89C7AF41DF2147450CC5@utd59514.utdallas.edu>
In-Reply-To: <47605C8C.4010601@123.com.sv>
References:  <4760208B.5060707@123.com.sv> <192E5FCC5BDD87CAD2C1341E@utd59514.utdallas.edu> <47604075.8060705@123.com.sv> <18272.17315.714141.372324@jerusalem.litteratus.org> <47604DE2.4010307@123.com.sv> <20071212211342.GA11906@gizmo.acns.msu.edu> <47605C8C.4010601@123.com.sv>

next in thread | previous in thread | raw e-mail | index | archive | help
--On Wednesday, December 12, 2007 16:11:24 -0600 Cesar Amaya=20
<csar@123.com.sv> wrote:

>
>> Looks like something, maybe your mail program has a large file open -
>> maybe trying to receive a huge file.   Killing the process could get
>> that file closed and either it would be gone or would finally show
>> how much space it is holding.
>>
>> ////jerry
>>
>>
>
> I even restarted the server but the problem is still there.
> this is what I got every amount of time (not always).
>
> root     mail.local  8987    3 /tmp          4 -rw-------  616886272 rw
>
> I don=C2=B4t understand why mail.local is gathering a file that big
>
>

Yikes!  Looks like whatever that message is is being retried by the sending =

MTA.  Perhaps you could try deleting the message from the queue.  (I assume =

it will sit in there until delivery is successful.)

I think, if you shut the mail server down and then restart it later, you're =

going to continue to have this problem.  You may have to figure out where=20
the message is coming from and try to stop it at the other end.  Possibly=20
you could configure your server to reject messages larger than a certain=20
size, then restart it and let it reject it rather than trying to receive=20
it.  I know you can do that with Postfix.  Don't know about other MTAs.

One thing I would do is stop the mail server, wait a minute or two, and=20
then check /tmp.  This would positively confirm that the problem is coming=20
from the mail server *if* the problem goes away when the server is stopped.

--=20
Paul Schmehl (pauls@utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/




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