Re: Repairing a table
Ian Barnes wrote: Im having another problem with a large db. I have a 160Gig drive dedicated to the database partition and I have on database in particular that is taking up the space. My .MYD is 78Gig and my .MYI is 34 gig. Thats fine i have a couple of gig left, but whenever i try and do anything on it, the disk fills up and I have to run a repair table tablename quick to get it going and that takes forever since its quite large. What kind of filesystem is this? I suggest running Linux, and using a sensible filesystem like XFS, possibly Repairing tables take a long time usually (Falcon is meant to fix this)... Do you know why the disk is filling up so fast? What MySQL version is this? And how much *actual* free space do you have? -- Colin Charles, Community Engineer MySQL AB, Melbourne, Australia, www.mysql.com Mobile: +614 12 593 292 / Skype: colincharles Web: http://www.bytebot.net/blog/ MySQL Forge: http://forge.mysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Repairing a table
Hi, Im having another problem with a large db. I have a 160Gig drive dedicated to the database partition and I have on database in particular that is taking up the space. My .MYD is 78Gig and my .MYI is 34 gig. Thats fine i have a couple of gig left, but whenever i try and do anything on it, the disk fills up and I have to run a repair table tablename quick to get it going and that takes forever since its quite large. Is there any other way that I could repair the index's quickly without having to wait up to 48 hours for the index to repair? Also, if i run out of diskspace, is there any way that I can get it working without truncating the data? Thanks alot Ian
Repairing InnoDB table
Hello, I have a database using a few InnoDB tables. The database has not been in use for a while and now I noticed that all InnoDB tables in the database cannot be opened and used at all. Whatever I try to do, I got Can't open asiakkaat.InnoDB (errno: 1) error. I'd like to know, how could I repair the tables and get even the structure copied. I took a look to the data files and there are .frm files for the tables available. Thank you for help, Ville Mattila -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Repairing InnoDB table
Have the ib* files been removed or damaged? Depending on your configuration, these coulde exists in your mysql data directory. -Original Message- From: Ville Mattila To: [EMAIL PROTECTED] Sent: 4/28/04 5:28 AM Subject: Repairing InnoDB table Hello, I have a database using a few InnoDB tables. The database has not been in use for a while and now I noticed that all InnoDB tables in the database cannot be opened and used at all. Whatever I try to do, I got Can't open asiakkaat.InnoDB (errno: 1) error. I'd like to know, how could I repair the tables and get even the structure copied. I took a look to the data files and there are .frm files for the tables available. Thank you for help, Ville Mattila -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
repairing MyISAM table kills mysqld with SIG11
Description: 010827 16:24:44 Warning: Retrying repair of: './Mloti/blast_data' with keycache mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked agaist 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=268431360 record_buffer=4190208 sort_buffer=67108856 max_used_connections=6 max_connections=100 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 3030635 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 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 range sanity check OK, backtrace follows: 0x807b0b8 0x812a6fa 0x8150f4f 0x81141dc 0x8108a84 0x80c4268 0x80c3f6e 0x80cacd0 0x80cd9e6 0x8082421 0x8085476 0x8080b4d 0x808006e Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the sta ck trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x859ead0 = repair TABLE blast_data thd-thread_id=268 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 268 did to cause the crash. In some cases of really bad corruption, the above values may be invalid Please use the information above to create a repeatable test case for the crash, and send it to [EMAIL PROTECTED] Number of processes running now: 0 010827 16:24:44 mysqld restarted How-To-Repeat: /usr/local/mysql-3.23.39/bin/mysqlcheck -r --compress Mloti Mloti.Upd OK Mloti.blastOK Mloti.blast_crossupdateOK Mloti.blast_crossupdate_data OK /usr/local/mysql-3.23.39/bin/mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'REPAIR TABLE' mysql check TABLE blast_data; +--+---+--+---+ | Table| Op| Msg_type | Msg_text | | +--+---+--+---+ | Mloti.blast_data | check | warning | Table is marked as crashed and last repair |failed | | Mloti.blast_data | check | warning | Size of datafile is: 178083072 Should |be: 178083068 | | Mloti.blast_data | check | error| Can't read indexpage from filepos: -1 | | | Mloti.blast_data | check | error| Corrupt | | +--+---+--+---+ 4 rows in set (0.01 sec) mysql optimize TABLE blast_data; +--+--+--+-+ | Table| Op | Msg_type | Msg_text || +--+--+--+-+ | Mloti.blast_data | optimize | error| Can't open file: 'blast_data.MYD'. (errno: |144) | +--+--+--+-+ 1 row in set (0.00 sec) mysql repair TABLE blast_data; ERROR 2006: MySQL server has gone away No connection. Trying to reconnect... Connection id:268 Current database: Mloti Resolved stack trace generated with the mysqlcheck utility (stack trace generated by `REPAIR TABLE blast_data' seems exactly same). kulan$ nm -n /usr/local/mysql-3.23.39/libexec/mysqld symbol.table kulan$ /usr/local/mysql-3.23.39/bin/resolve_stack_dump -s symbol.table -n stack 0x807b0b8 handle_connections_sockets__FPv + 948 0x812a6fa uncompress + 122 0x8150f4f ptmalloc_init_all + 7 0x81141dc ptr_compare_2 + 0 0x8108a84 sort_write_record + 856 0x80c4268 rnd_pos__12ha_myisammrgPcT1 + 44 0x80c3f6e create__12ha_myisammrgPCcP8st_tableP24st_ha_create_information + 70 0x80cacd0 mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13st_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10Alter_dr + 7464 0x80cd9e6 read_field__9READ_INFO + 358 0x8082421 mysql_execute_command__Fv + 9845 0x8085476 yyparse__Fv + 4870 0x8080b4d mysql_execute_command__Fv + 3489 0x808006e mysql_execute_command__Fv + 706 kulan$ mysql-3.23.39 has been compiled on thjis machine running currently 2.2.19 kernel (linux
Re: repairing MyISAM table kills mysqld with SIG11
Hi! Try to repair the same table with 3.23.41. If it fails, please let us know, so that we can give you upload instructions. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11
On Mon, 27 Aug 2001, Sinisa Milivojevic wrote: Hi! Try to repair the same table with 3.23.41. If it fails, please let us know, so that we can give you upload instructions. kulan$ ls -la /home/mysql/Mbovis/cogs_data* -rw-rw1 pedant users54195408 Jul 4 03:52 /home/mysql/Mbovis/cogs_data.MYD -rw-rw1 pedant users 72704 Aug 27 18:44 /home/mysql/Mbovis/cogs_data.MYI -rw-rw1 pedant users8714 Jul 4 03:52 /home/mysql/Mbovis/cogs_data.frm 3.23.41 also fails: mysql use Mbovis; Database changed mysql check table cogs_data; +--+---+--+-+ | Table| Op| Msg_type | Msg_text | | +--+---+--+-+ | Mbovis.cogs_data | check | warning | Table is marked as crashed and last repair |failed | | Mbovis.cogs_data | check | warning | Size of indexfile is: 72704 Should be: |25600 | | Mbovis.cogs_data | check | warning | Size of datafile is: 54195408 Should be: |54195388 | | Mbovis.cogs_data | check | error| Found 3277 keys of 257 | | | Mbovis.cogs_data | check | error| Corrupt | | +--+---+--+-+ 5 rows in set (0.05 sec) mysql repair table cogs_data; ERROR 2013: Lost connection to MySQL server during query mysql quit 0x8079ab8 handle_segfault__Fi + 380 0x8128eba pthread_sighandler + 150 0x814f0b6 chunk_free + 222 0x8151203 free + 155 0x8111cdc my_no_flags_free + 16 0x8106684 mi_repair + 2220 0x80c28e8 repair__9ha_myisamP3THDR17st_mi_check_paramb + 624 0x80c25ee repair__9ha_myisamP3THDP15st_ha_check_opt + 286 0x80c9430 mysql_admin_table__FP3THDP13st_table_listP15st_ha_check_optPCc13thr_lock_typebT5UiPM7handlerFP7handlerP3THDP15st_ha_check_opt_i + 1432 0x80cc173 mysql_repair_table__FP3THDP13st_table_listP15st_ha_check_opt + 67 0x8080fb1 mysql_execute_command__Fv + 4117 0x8083fa2 mysql_parse__FP3THDPcUi + 210 0x807f6bd do_command__FP3THD + 1269 0x807ebbb handle_one_connection__FPv + 551 Binaries produced on the problematic machine (Redhat 6.2), 2.2.19: CFLAGS=-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti CXX=gcc CXXFLAGS=-O3 -mpentiumpro -feli de-constructors -fno-exceptions -fno-rtti ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld -ldflags=-all-static -with-libwrap -with-named-z-lib --with-charset=latin1 --enable-thread-safe-client --with-nam ed-curses-libs=/usr/local/lib/libncurses.a --with-pthread If I should try also your binary distribution, please let me know. -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs [EMAIL PROTECTED] Faculty of Science, The Charles University - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11
=?iso-8859-2?Q?Martin_MOKREJ=A9?= writes: On Mon, 27 Aug 2001, Sinisa Milivojevic wrote: If I should try also your binary distribution, please let me know. -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs [EMAIL PROTECTED] Faculty of Science, The Charles University Hi! Please try out our binary distro. I guess that you would not like either that we spend our time on fixing something that should not be fixed. If that repair crashes our latest binary, make a tar.gz out of your table and upload it to: ftp://support.mysql.com/pub/mysql/secret And send me a direct mail with a name of your tarball. Thanks in advance. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11
cut Can you upload a copy of blast_data to ftp://support.mysql.com/pub/mysql/secret after verify first that what you plan to upload will crash a separate MySQL server on REPAIR? -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11 (fwd)
Hi, sorry I did not send the last e-mail to the whole list, so here it is. -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs [EMAIL PROTECTED] Faculty of Science, The Charles University -- Forwarded message -- Date: Mon, 27 Aug 2001 17:39:07 +0200 (MET DST) From: Martin MOKREJ [EMAIL PROTECTED] To: Sinisa Milivojevic [EMAIL PROTECTED] Subject: Re: repairing MyISAM table kills mysqld with SIG11 On Mon, 27 Aug 2001, Sinisa Milivojevic wrote: Please try out our binary distro. I guess that you would not like either that we spend our time on fixing something that should not be fixed. OK, so this is from mysql-3.23.41-pc-linux-gnu-i686/bin/mysqld.sym.gz et al.: mysql check table cogs_data; +--+---+--+-+ | Table| Op| Msg_type | Msg_text | | +--+---+--+-+ | Mbovis.cogs_data | check | warning | Table is marked as crashed and last repair |failed | | Mbovis.cogs_data | check | warning | Size of indexfile is: 72704 Should be: |25600 | | Mbovis.cogs_data | check | warning | Size of datafile is: 54195408 Should be: |54195388 | | Mbovis.cogs_data | check | error| Found 3277 keys of 257 | | | Mbovis.cogs_data | check | error| Corrupt | | +--+---+--+-+ 5 rows in set (0.55 sec) mysql repair table cogs_data; ERROR 2013: Lost connection to MySQL server during query mysql quit 0x807b1b8 handle_segfault__Fi + 380 0x812af8a pthread_sighandler + 154 0x81517df free + 39 0x8114a6c my_no_flags_free + 16 0x8109304 mi_repair + 2236 0x80c4768 repair__9ha_myisamP3THDR17st_mi_check_paramb + 624 0x80c446e repair__9ha_myisamP3THDP15st_ha_check_opt + 286 0x80cb320 mysql_admin_table__FP3THDP13st_table_listP15st_ha_check_optPCc13thr_lock_typebT5UiPM7handlerFP7handlerP3THDP15st_ha_check_opt_i + 1432 0x80ce076 mysql_repair_table__FP3THDP13st_table_listP15st_ha_check_opt + 70 0x8082641 mysql_execute_command__Fv + 4133 0x80856a6 mysql_parse__FP3THDPcUi + 210 0x8080d2d do_command__FP3THD + 1261 0x808022c handle_one_connection__FPv + 548 If that repair crashes our latest binary, make a tar.gz out of your table and upload it to: ftp://support.mysql.com/pub/mysql/secret kulan$ ftp support.mysql.com Connected to support.mysql.com. 220 www.mysql.com FTP server ready. Name (support.mysql.com:pedant): ftp 331 Guest login ok, send your complete e-mail address as password. Password: 530 Can't set guest privileges. Login failed. ftp user anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 530 Can't set guest privileges. Login failed. ftp And send me a direct mail with a name of your tarball. http://pednew.gsf.de/cogs_data.tgz Please let me know that I can remove the file. ;) Thanks! -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs [EMAIL PROTECTED] Faculty of Science, The Charles University - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11 (fwd)
On Mon, 27 Aug 2001, Martin MOKREJ wrote: ftp://support.mysql.com/pub/mysql/secret Hmm, I can already login as ftp, but can only chdir to /pub/mysql, there's no secret directory. ;( http://pednew.gsf.de/cogs_data.tgz Hmm, try out http://kulan.gsf.de/cogs_data.tgz , but I'm sure the previous worked for me. ;-) Do you have it? -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs [EMAIL PROTECTED] Faculty of Science, The Charles University - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11 (fwd)
mysql repair table cogs_data; ERROR 2013: Lost connection to MySQL server during query mysql quit 0x807b1b8 handle_segfault__Fi + 380 0x812af8a pthread_sighandler + 154 0x81517df free + 39 0x8114a6c my_no_flags_free + 16 0x8109304 mi_repair + 2236 0x80c4768 repair__9ha_myisamP3THDR17st_mi_check_paramb + 624 0x80c446e repair__9ha_myisamP3THDP15st_ha_check_opt + 286 0x80cb320 mysql_admin_table__FP3THDP13st_table_listP15st_ha_check_optPCc13t= hr_lock_typebT5UiPM7handlerFP7handlerP3THDP15st_ha_check_opt_i + 1432 0x80ce076 mysql_repair_table__FP3THDP13st_table_listP15st_ha_check_opt + 70 0x8082641 mysql_execute_command__Fv + 4133 0x80856a6 mysql_parse__FP3THDPcUi + 210 0x8080d2d do_command__FP3THD + 1261 0x808022c handle_one_connection__FPv + 548 =20 If that repair crashes our latest binary, make a tar.gz out of your table and upload it to: =20 ftp://support.mysql.com/pub/mysql/secret kulan$ ftp support.mysql.com Connected to support.mysql.com. 220 www.mysql.com FTP server ready. Name (support.mysql.com:pedant): ftp 331 Guest login ok, send your complete e-mail address as password. Password: 530 Can't set guest privileges. Login failed. ftp user anonymous 331 Guest login ok, send your complete e-mail address as password. Password:=20 530 Can't set guest privileges. Login failed. ftp Sorry about that - we have now fixed the problems with our anonymous FTP upload, and it should be working. -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11 (fwd)
Sorry about that - we have now fixed the problems with our anonymous FTP upload, and it should be working. lokk in pub/mysql/secret/ for: 15593452(size) cogs_data.tgz But same file should be accessible already via the 2 web links I've sent to you via personal e-mail. Thanks. -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs [EMAIL PROTECTED] Faculty of Science, The Charles University - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: repairing MyISAM table kills mysqld with SIG11 (fwd)
On Monday 27 August 2001 12:30, Martin MOKREJ? wrote: Sorry about that - we have now fixed the problems with our anonymous FTP upload, and it should be working. lokk in pub/mysql/secret/ for: 15593452(size) cogs_data.tgz But same file should be accessible already via the 2 web links I've sent to you via personal e-mail. Thanks. Thanks. Monty or Sergei - can you take a look at it - repair table cogs_data; dumps core with the following backtrace: 0x807b1b8 handle_segfault__Fi + 380 0x812af8a pthread_sighandler + 154 0x81517df free + 39 0x8114a6c my_no_flags_free + 16 0x8109304 mi_repair + 2236 0x80c4768 repair__9ha_myisamP3THDR17st_mi_check_paramb + 624 0x80c446e repair__9ha_myisamP3THDP15st_ha_check_opt + 286 0x80cb320 mysql_admin_table__FP3THDP13st_table_listP15st_ha_check_optPCc13thr_lock_typebT5UiPM7handlerFP7handlerP3THDP15st_ha_check_opt_i + 1432 0x80ce076 mysql_repair_table__FP3THDP13st_table_listP15st_ha_check_opt + 70 0x8082641 mysql_execute_command__Fv + 4133 0x80856a6 mysql_parse__FP3THDPcUi + 210 0x8080d2d do_command__FP3THD + 1261 0x808022c handle_one_connection__FPv + 548 -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Repairing a table?
I'm running mysql v3.22.32 and encountered a corrupt key file for a table. I searched the documentation on the site, but it doesn't seem to pertain to this version of mysql any longer. I'm hesitant to upgrade to 3.23.32 until I can figure out what it might break. Does anyone have the steps that will allow me to repair a db table for 3.22.32? - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Repairing a table?
I'm running mysql v3.22.32 and encountered a corrupt key file for a table. I searched the documentation on the site, but it doesn't seem to pertain to this version of mysql any longer. I'm hesitant to upgrade to 3.23.32 until I can figure out what it might break. Does anyone have the steps that will allow me to repair a db table for 3.22.32? The documentation that you should use when you have an older version of mysql is the documentation that came with your copy. You should do this to replair a table shutdown the mysqld daemon isamchk -r tablename.ISM make sure everything is repaird according to isamchk ouput start the mysqld daemon. my problem with the docs on the site was that they said myisamchk and the rpms for 3.22 had isamchk, so of course that command doesn't work, heheh. Thanks. The table is repaired and working once again. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
