SQL Database doesn’t work right why? - SQL Server Forums

Home | Weblogs | Forums

Site Sponsored By: SQLDSC - SQL Server Desired State Configuration

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

SQL Database doesn’t work right why?

Author

Topic

CliffordPreston
Starting Member

1 Post

Posted - 2014-09-23 : 11:21:39

Hi Everyone!
The problem follows. I decided myself to add space to one section. Booted from LiveCd, launched gparted, pitched wrong. After rebooting fell lilo, but to this I was ready and fixed the problem, but what was not ready, so this is a fact that is impossible to start mysql. Digging in his logs showed that the problem in the database itself. If you delete a folder with the base and through the mysql_install_db script to re-do, then run mysql, but how to restore the old one? And as a rhetorical question - why it stopped working due to actions directly associated with it?
Can provide (if necessary) the error log.

130908 02:10:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130908 2:10:14 InnoDB: The InnoDB memory heap is disabled
130908 2:10:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130908 2:10:14 InnoDB: Compressed tables use zlib 1.2.5
130908 2:10:14 InnoDB: Using Linux native AIO
130908 2:10:14 InnoDB: Initializing buffer pool, size = 128.0M
130908 2:10:14 InnoDB: Completed initialization of buffer pool
130908 2:10:14 InnoDB: highest supported file format is Barracuda.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 273.
InnoDB: You may have to recover from a backup.
130908 2:10:14 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex b037d23e00000111...????? 0 ? f
37f3aea922e56d3a; asc 7 > " m: + x - 2
7 " m:;
InnoDB: End of page dump
130908 2:10:14 InnoDB: Page checksum 741347838, prior-to-4.0.14-form checksum 938716841
InnoDB: stored checksum 2956448318, prior-to-4.0.14-form stored checksum 938716841
InnoDB: Page lsn 0 585461050, low 4 bytes of lsn at page end 585461050
InnoDB: Page number (if stored to page already) 273,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 273.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
130908 2:10:14 InnoDB: Assertion failure in thread 140161815877440 in file buf0buf.c line 3602
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.
22:10:14 UTC - 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=16384
read_buffer_size=262144
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 = 50057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x20000
/usr/bin/mysqld(my_print_stacktrace+0x29)[0x757339]
/usr/bin/mysqld(handle_fatal_signal+0x367)[0x64f5c7]
/lib64/libpthread.so.0(+0xf4e0)[0x7f79f70004e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f79f59fba25]
/lib64/libc.so.6(abort+0x148)[0x7f79f59fd1d8]
/usr/bin/mysqld[0x7d3bd1]
/usr/bin/mysqld[0x7de348]
/usr/bin/mysqld[0x7dec37]
/usr/bin/mysqld[0x7cf655]
/usr/bin/mysqld[0x7a33cf]
/usr/bin/mysqld[0x7a40b6]
/usr/bin/mysqld[0x7a589d]
/usr/bin/mysqld[0x793671]
/usr/bin/mysqld[0x761110]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x6513f1]
/usr/bin/mysqld[0x57ce95]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0x7d8)[0x580cc8]
/usr/bin/mysqld[0x50cf9d]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x393)[0x510e83]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f79f59e6a95]
/usr/bin/mysqld[0x5097e5]

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2014-09-23 : 12:08:15

Looks like you are using MySql. SQLTeam.com is for Microsoft SQL Server. You'll want to post your question on a site that specializes in MySql.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/

prett
Posting Yak Master

212 Posts

Posted - 2014-09-28 : 23:45:39

This is a MS SQL Server forum, in general we are not expert in MySQL database. Try asking your question at MySQL related forum like http://forums.mysql.com/

Lincolnburrows
Yak Posting Veteran

52 Posts

Posted - 2014-09-29 : 06:20:39

You need to go to MySQL database forums

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources