Margrit, your disk or file system is probably broken:
> InnoDB: Fatal error: cannot read from file. OS error number 17. 17 EEXIST File exists The error number does not make sense in a file read. Strange. You cannot remove ib_logfiles from an InnoDB installation. They are as important as ibdata files. You can look at http://www.innodb.com/ibman.html#Forcing_recovery about emergency recovery using a recent MySQL-4.0 version. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: "Margrit Lottmann" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Friday, November 14, 2003 3:27 PM Subject: innodb-errors > Following errors we've got by restarting mysqld > > 031114 10:26:51 mysqld started > InnoDB: Fatal error: cannot read from file. OS error number 17. > 031114 10:26:56 InnoDB: Assertion failure in thread 1024 in file os0file.c line 1329 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > 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 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=8388600 > read_buffer_size=131072 > max_used_connections=0 > max_connections=100 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x83a9fb0 > 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... > Cannot determine thread, fp=0xbfffd058, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x80df7ea > 0x40035f05 > 0x82ac20c > 0x82acc41 > 0x825be18 > 0x820e66c > 0x816fb00 > 0x813d58a > 0x8138000 > 0x80e05f3 > 0x42017589 > 0x80a0da1 > New value of fp=(nil) failed sanity check, terminating stack trace! > Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack 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 (nil) is invalid pointer > thd->thread_id=1667594851 > The manual page at http://www.mysql.com/doc/en/Crashing.html contains > information that should help you find out what is causing the crash. > 031114 10:26:56 mysqld ended > > > > We have done recovery by using ibdata1 file from current update (by > removing logfiles > > ...mysqld startet ok ...working for recovery ...but stopped if any select > request to an InnoDB table was executed. > > Following trace-results we've got by using resove-tool... > > 0x80df7ea handle_segfault + 398 > 0x40035f05 _end + 935903133 > 0x81b5384 row_search_for_mysql + 5856 > 0x813f6e8 index_read__11ha_innobasePcPCcUi16ha_rkey_function + 644 > 0x8142c0f index_first__11ha_innobasePc + 35 > 0x8142d09 rnd_next__11ha_innobasePc + 41 > 0x8135704 rr_sequential__FP14st_read_record + 144 > 0x811311b join_init_read_record__FP13st_join_table + 75 > 0x810d346 sub_select__FP4JOINP13st_join_tableb + 78 > 0x810d101 do_select__FP4JOINPt4List1Z4ItemP8st_tableP9Procedure + 393 > 0x81060bb mysql_select__FP3THDP13st_table_listRt4List1Z4ItemP4ItemP8st_orderT4T3T4UlP1 3select_result + 8683 > 0x81128cc handle_select__FP3THDP6st_lexP13select_result + 92 > 0x80ea8f2 mysql_execute_command__Fv + 978 > 0x80ee2bd mysql_parse__FP3THDPcUi + 349 > 0x80e9c68 dispatch_command__F19enum_server_commandP3THDPcUi + 1244 > 0x80ef85d do_command__FP3THD + 149 > 0x80e90e0 handle_one_connection + 584 > 0x40032faf _end + 935891015 > 0x420e790a _end + 970185122 > > How can we resolve our problems??? > > > -- > Mit freundlichen Gruessen > M.Lottmann > > Otto - von - Guericke Universitaet __ __ ____ _____ _ __ > Magdeburg / / / / / __ \__ / / | / / > ------------------------------------ / / / / / /_/ / / / ______ / |/ / > Margrit Lottmann / /_/ / / _, _/ / /_______// /| / > Universitaetsrechenzentrum \____/ /_/ |_| /____/ /_/ |_/ > Netze & Kommunikation > > > -- > 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]
