MySQL Forums
Forum List  »  InnoDB

Re: Problem of data corruption
Posted by: Cristian Sergiu
Date: March 31, 2005 01:04PM

Dear everybody :),

I have got this message:

050331 21:40:20 InnoDB: Started
mysqld-nt: ready for connections.
Version: '4.0.12-nt' socket: '' port: 3306
InnoDB: Error on pages 5897 and 5900 in index PRIMARY table comat/elemente_trans
fer
InnoDB: records in wrong order on adjacent pages
050331 21:40:50 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 0000000000001709000012ba0000170c000000002555a6a145bf000000000000
00000000000000143bbe004f009d018a00000002004a004b00000000000000000000000000000000
09d9000000000000044a1172000000000000044a10b208010000030227696e66696d756d00090400



etc......etc...hex.....



.i.e.].L.;.*.&.$. ............¿&?.Ü╥tτ....∙.... .(¬SMXJH4453751.¬O...yM6....
467400.000 2460000.000 2927400.000TIPARITA...~........Ü╥tΣSe achita
pana la data 15/02/2005.¬O...û.u.q.m.i.e.].L.;.*.&.$. ............░&..Ü╥u.....∙
ò... .)éSMXJH4453752.¬OÜ╥u.M6.... 32651.000 171849.000 204
500.000TIPARITA...~........Ü╥u.Se achita pana la data 15/02/2005.¬OTA.¬d .t9.7T5
î3─.t...├.{.3.δ.ú.[...╦.â.;.≤.½.c...╙.ï.C.√.│.k.#.█.ô.K...╗.eó└½U%ë@B;InnoDB: En
d of page dump
050331 21:42:18 InnoDB: Page checksum 2730535765 stored checksum 2730535765
InnoDB: Page lsn 0 629751874, low 4 bytes of lsn at page end 629751874
InnoDB: Page may be an index page where index id is 0 2582
InnoDB: record RECORD: info bits 0 0: len 4; hex 804d7f75; asc .M.u;; 1: len 6;
hex 0000011c8a70; asc ....èp;; 2: len 7; hex 80000014380699; asc ....8..;; 3: le
n 4; hex 804d7f04; asc .M..;; 4: len 4; hex 800000da; asc ...┌;; 5: len 4; hex 8
00002cd; asc ...═;; 6: len 22; hex 202020202020202020202020202020312e3030303030;
asc 1.00000;; 7: len 22; hex 202020202020202020202034363334342e3
534303030; asc 46344.54000;; 8: len 22; hex 2020202020202020202020343
63334342e3534303030; asc 46344.54000;; 9: len 22; hex 202020202020202
020202036333030302e3030303030; asc 63000.00000;; 10: len 22; hex 2020
20202020202020202034363334342e3534303030; asc 46344.54000;; 11: len 4
; hex 80000000; asc ....;; 12: len 22; hex 202020202020202020202036333030302e303
0303030; asc 63000.00000;;
InnoDB: record RECORD: info bits 16 0: len 6; hex 0000000950e4; asc ... PΣ;; 1:
len 4; hex 00001710; asc ....;;
050331 21:42:18 InnoDB: Assertion failure in thread 2572 in file D:\mysql-4.0.1
2\innobase\btr\btr0cur.c line 192
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
InnoDB: Thread 684 stopped in file D:\mysql-4.0.12\innobase\sync\sync0arr.c line
126



I am using mysqld-nt Ver 4.0.12-nt for NT on i32
and my config file lok like this :


# Example mysql config file.
# Copy this file to c:\my.cnf to set global options
#
# One can use all long options that the program supports.
# Run the program with --help to get a list of available options

# This will be passed to all mysql clients
[client]
#password=my_password
port=3306
#socket=MySQL

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# The MySQL server
[mysqld]
port=3306
#socket=MySQL
skip-locking
set-variable = key_buffer=16M
set-variable = max_allowed_packet=128M
set-variable = table_cache=512
set-variable = sort_buffer=8M
set-variable = record_buffer=8M
set-variable = thread_cache=8
set-variable = max_heap_table_size=32M
# Try number of CPU's*2 for thread_concurrency
set-variable = thread_concurrency=8
set-variable = myisam_sort_buffer_size=4M
server-id = 1

# Uncomment the following if you want to log updates
#log-bin

# Uncomment the following rows if you move the MySQL distribution to another
# location
#basedir = d:/mysql/
#datadir = d:/mysql/data/


# Uncomment the following if you are NOT using BDB tables
#skip-bdb

# Uncomment the following if you are using BDB tables
#set-variable = bdb_cache_size=384M
#set-variable = bdb_max_lock=100000

#innodb_force_recovery = 4
# Uncomment the following if you are using Innobase tables
#innodb_data_file_path = ibdata1:2000M;ibdata2:2000M
#innodb_data_home_dir = c:\ibdata
#innodb_log_group_home_dir = c:\iblogs
#innodb_log_arch_dir = c:\iblogs
#set-variable = innodb_mirrored_log_groups=1
#set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=5M
set-variable = innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=128M
set-variable = innodb_additional_mem_pool_size=16M
#set-variable = innodb_file_io_threads=16
#set-variable = innodb_lock_wait_timeout=50

[mysqldump]
quick
set-variable = max_allowed_packet=16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
set-variable = key_buffer=256M
set-variable = sort_buffer=256M
set-variable = read_buffer=2M
set-variable = write_buffer=2M

[myisamchk]
set-variable = key_buffer=256M
set-variable = sort_buffer=256M
set-variable = read_buffer=2M
set-variable = write_buffer=2M

[mysqlhotcopy]
interactive-timeout


How can i know if it is a hardware or a system error or mysq bug???
Please help me...

Options: ReplyQuote


Subject
Views
Written By
Posted
4265
January 21, 2005 07:49AM
2694
January 21, 2005 07:53AM
2635
January 21, 2005 03:52PM
2578
January 25, 2005 04:57PM
2821
January 27, 2005 02:55AM
2725
February 16, 2005 07:58AM
2513
February 25, 2005 06:54AM
2544
March 03, 2005 03:07AM
2742
February 16, 2005 11:15AM
3503
February 17, 2005 03:40AM
2545
February 17, 2005 03:25PM
2542
March 17, 2005 01:55AM
2549
March 18, 2005 11:19AM
Re: Problem of data corruption
2861
March 31, 2005 01:04PM
2580
April 04, 2005 08:21AM
2766
April 04, 2005 09:24AM
2946
April 04, 2005 11:38PM
2582
April 19, 2005 09:47AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.