AdamDresch

Well-Known Member
Jun 22, 2006
80
0
156
No idea why this is suddenly an issue, but earlier today a few database tables came up as marked as crashed

So I shut down Mysql, ran a repair/optimise on all and everything seemed ok

An hour later, some more tables came up with marked as crashed

I checked the logs and saw lots of errors like this:

Code:
130318 16:33:56 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './x/jos_session.MYI'; try to repair it
and
130318 16:34:06 [ERROR] /usr/sbin/mysqld: Table './x/jos_session' is marked as crashed and should be repaired
I checked the tmp folder, it had some 899mb free, so it wasn't that, but repairing, the tables just didn't seem to "hold"

I've now changed the mysql tmp folder to another location, which seems to have fixed that issue

But now I'm noticing other errors about tmp being full when it isn't

Such as:

Code:
[Wed Mar 20 13:06:10 2013] [warn] [client 66.249.73.91] mod_fcgid: stderr: PHP Warning:  Unknown: open(/tmp/sess_aef044dfe3defd98e6931b4df9c19e8d, O_RDWR) failed: No space left on device (28) in Unknown on line 0
[Wed Mar 20 13:06:10 2013] [warn] [client 66.249.73.91] mod_fcgid: stderr: PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0
I'm running CentOS 6.4 X86_64, on a Xen VPS
 

AdamDresch

Well-Known Member
Jun 22, 2006
80
0
156
/usr/tmpDSK 59264 4382 54882 8% /tmp

Hmm mind you, I have just moved all mysql/php temp files to a new directory.
So that might solve it for the time being

Thanks InterServed.