Note about MySQL rebuilding a damaged index.

This commit is contained in:
hjp 2010-06-16 08:28:44 +00:00
parent 259d97bc99
commit 5953f4048a
1 changed files with 28 additions and 0 deletions

28
Notes
View File

@ -84,3 +84,31 @@ Ideas:
* Check if File::Path behaves better.
* Die on error and let caller catch the error.
MySQL after crash:
-rw-rw---- 1 mysql mysql 10034184192 2010-06-07 09:14 instances.MYD
drwxr-xr-x 8 mysql mysql 4096 2010-06-07 10:20 ../
-rw-rw---- 1 mysql mysql 297649152 2010-06-07 10:20 files.MYI
-rw-rw---- 1 mysql mysql 619416576 2010-06-07 21:03 versions2.MYI
-rw-rw---- 1 mysql mysql 6144 2010-06-15 21:00 sessions.MYI
-rw-rw---- 1 mysql mysql 42952 2010-06-15 21:00 sessions.MYD
-rw-rw---- 1 mysql mysql 20630449152 2010-06-16 10:21 instances.MYI
mri:/var/lib/mysql/simba 10:21 :-) 108# df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/mri.wsr.ac.at-mysql
41284928 32332032 6856220 83% /var/lib/mysql
mri:/var/lib/mysql/simba 10:21 :-) 109# psg backup
root 19827 0.0 0.0 10100 1052 ? Ss Jun07 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 19407 0.0 0.0 10100 2136 ? Ss Jun08 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 3993 0.0 0.0 10100 2136 ? Ss Jun09 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 26324 0.0 0.0 10100 2552 ? Ss Jun10 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 16156 0.0 0.0 10100 2728 ? Ss Jun11 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 462 0.0 0.0 10100 2136 ? Ss Jun12 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 17584 0.0 0.0 10100 2748 ? Ss Jun13 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 1607 0.0 0.0 10100 2716 ? Ss Jun14 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 21566 0.0 0.0 10100 2692 ? Ss Jun15 0:00 | \_ /usr/bin/perl /usr/local/bin/backup
root 18685 0.0 0.0 4352 1188 pts/5 S+ 10:22 0:00 \_ /bin/sh /usr/bin/psg backup
Looks like it has been rebuilding that index for the last 9 days. That's
clearly inacceptable.