maysql

[phrozen]

log maysql:

130629 23:00:43 mysqld started
130629 23:00:43 InnoDB: Started; log sequence number 1 2551397919
130629 23:00:43 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.0.92' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-5.0.92
130709 15:32:50 [ERROR] Error in accept: Software caused connection abort
130912 18:30:02 [ERROR] /usr/local/libexec/mysqld: Incorrect key file for table '/var/tmp/#sql_37b_0.MYI'; try to repair it
130912 18:45:00 [ERROR] /usr/local/libexec/mysqld: Incorrect key file for table '/var/tmp/#sql_37b_0.MYI'; try to repair it
130913 7:48:56 InnoDB: Error: Write to file ./ibdata1 failed at offset 0 2954887168.
InnoDB: 1048576 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/ ... codes.html
InnoDB: Starting shutdown...
130913 09:21:08 mysqld ended
130913 09:34:31 mysqld started
130913 9:34:31 InnoDB: Started; log sequence number 2 9010649
130913 9:34:31 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.0.92' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-5.0.92
131001 13:20:07 [ERROR] Error in accept: Software caused connection abort
131205 11:01:28 [Note] /usr/local/libexec/mysqld: Normal shutdown

/var ёмкость 6Гб

файл bdata1 весит 5,1 Гб

Помогите!

[ZeM]

1. Df -h и df -i, du -h /var/log/mysql, du -sh /var/lib/mysql, du -sh /var/lib/mysql/mysql-bin
2. Грохните логи mysql.
3. Если не поможет обновить mysql до 5.5

[Wishmaster]

Размер ibdata зависит от настроек, в частности от тех, которые регулируют использование памяти самой MySQL.

Смонтируйте отдельный раздел под БД. 6гб - мало. Тем более, для всего /var.

И еще, прежде чем запускать mysql, ребутните сервер в single user mode и сделайте:

fsck -y && reboot

Это исправит возможные ошибки ФС в разделе.