[H-GEN] MySQL filling up /

[Tony Melia]

Could it be that DU doesn't take open files into account, but DF does, and
mysql had 4G of files open?  Try 'lsof | grep mysql' and see if any of these
are large.

Regards,
TM

-----Original Message-----
From: general-bounces at lists.humbug.org.au
[mailto:general-bounces at lists.humbug.org.au] On Behalf Of Michael Anthon
Sent: Tuesday, 6 January 2004 3:46 PM
To: general at lists.humbug.org.au
Subject: [H-GEN] MySQL filling up /

[ Humbug *General* list - semi-serious discussions about Humbug and     ]
[ Unix-related topics. Posts from non-subscribed addresses will vanish. ]

I've come across an odd situation that I can't fully resolve.  We
noticed today that the root partition on one of our servers was full.
Investigation showed something a bit strange... du was reporting only 5G
used and df was reporting 9G used.  I've never seen such a large
discrepency between these 2 tools before.

In the end [1] I bounced the mysql server and all of a sudden I had 4G
free and df was reporting only 5G used.

A bit more searching showed others having similar problems but no real
definitive answers that I could find.  Mostly there was a recommendation
to set the mysql "tmpdir" to something other than /tmp, which is all
well and good but doesn't really explain what was happening.

The real thing I can't understand is how mysql was able to use up 4G of
space on the disk without me being able to find out where it was doing
it (and yes, tmpdir was set to /tmp and I know how to show hidden files)

Can anyone shed some light on this for me?

Cheers
Michael

[1] after trying lots of things like repeated du's and comparing
results, using "find -ctime -5.." etc etc.


_______________________________________________
General mailing list
General at lists.humbug.org.au
http://lists.humbug.org.au/cgi-bin/mailman/listinfo/general