forum.lissyara.su

Код: Выделить всё

111215 01:35:04 mysqld_safe Starting mysqld daemon with databases from /80gb/mysqldb
111215  1:35:04 [Warning] option 'thread_cache_size': unsigned value 16777216 adjusted to 16384
111215  1:35:04 InnoDB: The InnoDB memory heap is disabled
111215  1:35:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111215  1:35:04 InnoDB: Compressed tables use zlib 1.2.3
111215  1:35:04 InnoDB: Initializing buffer pool, size = 128.0M
111215  1:35:04 InnoDB: Completed initialization of buffer pool
111215  1:35:04 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 4295461191
111215  1:35:04  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 4295463613
111215  1:35:05  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 3
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 154263, file name ./mysql-bin.003664
111215  1:35:05  InnoDB: Waiting for the background threads to start
111215  1:35:06 InnoDB: 1.1.8 started; log sequence number 4295463613
111215  1:35:06 [Note] Recovering after a crash using mysql-bin
111215  1:35:06  InnoDB: Assertion failure in thread 1675470912 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
111215  1:35:06 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 572454 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

111215 01:35:06 mysqld_safe mysqld from pid file /80gb/mysqldb/adios.spb.ru.pid ended

Код: Выделить всё

The following warning/error was logged by the smartd daemon:
Device: /dev/ad3, ATA error count increased from 11 to 12

Код: Выделить всё

innodb_force_recovery = 2

Код: Выделить всё

mysqldump: Got error: 145: Table './mail/awm_messages' is marked as crashed and should be repaired when using LOCK TABLES