Hi,
I get unaligned access errors and I suspect mysqld to cause these, as it
reports page corruption just before. How would I find out whether this is
true?
is mysql-server-5.0 the package to file a bug report for the problem. What
else to include in the report?
mysql-Version: 5.0.32-7etch1
Description of what is happening:
mysqld finds a page corruption in a InnoDB database.
The kernel then reports an unaligned access.
mysqld restarts and performs the crash recovery.
unaligned access occurs again and ssh, ping, apache, mysql do not respond
anymore starting from this point.
Based on /var/log/syslog (see attachment) I suspect mysqld causes these
problems.
Any help would be appreciated
--
Dominik Reusser
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Database page corruption on disk or
a failed
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: file read of page 1672847.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: You may have to recover from a
backup.
Dec 10 10:11:44 libdb mysqld[3524]: 071210 10:11:43 InnoDB: Page dump in ascii
and hex (16384 bytes):
Dec 10 10:11:44 libdb mysqld[3524]: len 16384; hex c4deb3030
--snip-- ;InnoDB: End of page dump
Dec 10 10:11:44 libdb mysqld[3524]: 071210 10:11:44 InnoDB: Page checksum
2910718267, prior-to-4.0.14-form checksum 3244052608
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: stored checksum 3302929155,
prior-to-4.0.14-form stored checksum 126
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page lsn 49 3962043205, low 4 bytes
of lsn at page end 4096
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page number (if stored to page
already) 1672847,
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: space id (if created with >=
MySQL-4.1.1 and stored already) 0
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Page may be an index page where
index id is 0 523
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: (index LocatID_2 of table
iller/TBL_Sample)
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Database page corruption on disk or
a failed
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: file read of page 1672847.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: You may have to recover from a
backup.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: It is also possible that your
operating
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: system has corrupted its own file
cache
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: and rebooting your computer removes
the
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: error.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: If the corrupt page is an index page
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: you can also try to fix the
corruption
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: by dumping, dropping, and
reimporting
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: the corrupt table. You can use CHECK
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: TABLE to scan your table for
corruption.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: See also InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: about forcing recovery.
Dec 10 10:11:44 libdb mysqld[3524]: InnoDB: Ending processing because of a
corrupt database page.
Dec 10 10:11:45 libdb kernel: Kernel unaligned access at TPC[4c6af0]
do_task_stat+0x188/0x588
Dec 10 10:11:45 libdb kernel: Unable to handle kernel paging request in mna
handler<1> at virtual address 80a65493
Dec 10 10:11:45 libdb kernel: current->{active_,}mm->context = 099b
Dec 10 10:11:45 libdb kernel: current->{active_,}mm->pgd = f80016884000
Dec 10 10:11:45 libdb kernel: \|/ \|/
Dec 10 10:11:45 libdb kernel: "@'/ .. \`@"
Dec 10 10:11:45 libdb kernel: /_| \__/ |_\
Dec 10 10:11:45 libdb kernel: \__U_/
Dec 10 10:11:45 libdb kernel: ps(6642): Oops [#1]
Dec 10 10:11:45 libdb kernel: TSTATE: 004411009603 TPC: 004c6af0
TNPC: 004c6af4 Y: Not tainted
Dec 10 10:11:45 libdb kernel: TPC:
Dec 10 10:11:45 libdb kernel: g0: f800110dd000 g1: 0013 g2:
80a653e7 g3: 170008a0
Dec 10 10:11:45 libdb kernel: g4: f80011062980 g5: 73746174 g6:
f8001c66 g7: f8001fb41c60
Dec 10 10:11:45 libdb kernel: o0: f8001fc82500 o1: f8001c663c38 o2:
f8001c663c30 o3: f8001c663d48
Dec 10 10:11:45 libdb kernel: o4: 0252 o5: f80010d18800 sp:
f8001c6631c1 ret_pc: 004c6a3c
Dec 10 10:11:45 libdb kernel: RPC:
Dec 10 10:11:45 libdb kernel: l0: 0007 l1: f8001c663d48 l2:
f8001fb86e40 l3: 0013
Dec 10 10:11:45 libdb kernel: l4: 0011 l5: 0001 l6:
00030400 l7: 0053
Dec 10 10:11:45 libdb kernel: i0: f8001fc82500 i1: f800148ea000 i2:
0001 i3:
Dec 10 10:11:45 libdb kernel: i4: 0001 i5: i6:
f8001c663451 i7: 004c4aa0
Dec 10 10:11:45 libdb kernel
