What kernel are you running? Also, try increasing the max open tables. That might help.
Richard Gabriel Director of Technology, CoreSense Inc. (518) 306-3043 x3951 ----- Original Message ----- From: "Dathan Vance Pattishall" <[EMAIL PROTECTED]> To: "'Tom Roos'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, September 10, 2003 1:28 PM Subject: RE: "ERROR 1030: Got error 127 from table handler" > Filesystem Size Used Avail Use% Mounted on > /dev/sda5 97G 9.0G 82G 10% > > Plenty of disk space. > > -->-----Original Message----- > -->From: Tom Roos [mailto:[EMAIL PROTECTED] > -->Sent: Wednesday, September 10, 2003 10:23 AM > -->To: Dathan Vance Pattishall; [EMAIL PROTECTED] > -->Subject: RE: "ERROR 1030: Got error 127 from table handler" > --> > -->hows u're disk space? > --> > -->-----Original Message----- > -->From: Dathan Vance Pattishall [mailto:[EMAIL PROTECTED] > -->Sent: 10 September 2003 19:11 > -->To: [EMAIL PROTECTED] > -->Subject: "ERROR 1030: Got error 127 from table handler" > --> > --> > --> > -->/usr/local/mysql/bin/perror 127 > -->Error code 127: Unknown error 127 > -->127 = Record-file is crashed > --> > -->I've been getting this allot lately from mysql-3.23.54-57. > --> > --> > -->Things that are not the cause: > --> - mySQL has not been improperly shut down > --> - threads are not being killed off > --> > --> > -->Pattern emerged: > -->High Traffic DB up for a month or greater doing a constant 300 > -->queries/sec > --> > --> > -->Question: What is the cause of a Record-file crash? How can this be > -->prevented? Jeremy Zawodny do you have any thoughts on a root cause? > --> > --> > --> > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
