| Bug #52176 | MYSQL-NT goes in crash under windowxp | ||
|---|---|---|---|
| Submitted: | 18 Mar 2010 11:11 | Modified: | 24 Apr 2010 5:59 |
| Reporter: | Riccardo Centi | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 5.0.90 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | MYSQL-NT goes in crash under windowxp | ||
[18 Mar 2010 11:22]
Riccardo Centi
See BugData52176.zip in the FTP to replace exactly the bugs. You have to copy data of zip file in the right place (README.txt inside the zip file ) and the you have to try to create the table in the query. MYSQL 5.0.90 version.
[18 Mar 2010 17:06]
Riccardo Centi
I have upload trough FTP the file Bug-LogData-52176.zip for log file produced by MYSQL
[18 Mar 2010 18:19]
Sveta Smirnova
Thank you for the report. Prior to "trying to open" errors error log contains records: ----<q>---- 100318 7:58:50 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown 100318 7:58:51 InnoDB: Starting shutdown... 100318 7:58:53 InnoDB: Shutdown completed; log sequence number 13 2195417518 100318 7:58:53 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete 100318 8:04:15 InnoDB: Operating system error number 2 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html 100318 8:04:15 InnoDB: Error: trying to open a table, but could not InnoDB: open the tablespace file '.\psd\2010_03_18_blob.ibd'! InnoDB: Have you moved InnoDB .ibd files around without using the InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? InnoDB: It is also possible that this is a temporary table #sql..., InnoDB: and MySQL removed the .ibd file for this. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 100318 8:04:15 InnoDB: Operating system error number 2 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html 100318 8:04:15 InnoDB: Error: trying to open a table, but could not InnoDB: open the tablespace file '.\psd\2010_03_18_densita.ibd'! InnoDB: Have you moved InnoDB .ibd files around without using the InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? InnoDB: It is also possible that this is a temporary table #sql..., InnoDB: and MySQL removed the .ibd file for this. ----</q>---- So all errors started after shutdown of MySQL server. This looks like corruption happened outside of mysqld process. Have you moved *ibd files? Have you checked your hard disk?
[19 Mar 2010 7:45]
Riccardo Centi
I have read the log file before sending you all data , is not the first time I used MYSQL. Then I have used only query by MysqlBrowser. The error 80 is not enumerated in HTML Mysql 5.0.90 InnoDB Manual. Now MYSQL doesn't work in my computer if I don't remove manually all file from DB.
[19 Mar 2010 7:51]
Riccardo Centi
And in my opinion if MYSQL-NT display a 'blue' screen because is able to create a file in not a correct way to work....
[22 Mar 2010 8:24]
Sveta Smirnova
Thank you for the feedback. Have you moved *ibd files? Have you checked your hard disk?
[22 Mar 2010 9:47]
Riccardo Centi
The hard-disk have problems .... I have read from this publication : http://dev.mysql.com/doc/refman/5.5/en/forcing-recovery.html that MYSQL InnoDB go in crash if there is something wrong in table. MYSQL in my cause will be use in a program that cannot never stop also for Database faillure (because the target is finding material defect and DB is a secondary task). How can avoid 'blue screen' ?
[24 Mar 2010 5:59]
MySQL Verification Team
Your prior comment? "The hard-disk have problems .... I have read from this publication :" What is the hard drive problem?. Thanks in advance.
[24 Apr 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: The following query query failed (CREATE TABLE IF NOT EXISTS psd.2010_03_18_blob ( TempoDatabase DATETIME, time100ns BIGINT, identifier BIGINT , startx char (128) , endx char (128) , starttime char (128) , endtime char (128) , width char (128) , height char (128) , ricetta char (128) , classescarto char (128) , blobid char (128) , area char (128) , dimensionevalore BIGINT , valore LONGBLOB , primary key (time100ns,identifier) , key(time100ns) , key (TempoDatabase) , key(dimensionevalore) , key (startx) , key (endx) , key (starttime) , key (endtime) , key (width) , key (height) , key (ricetta) , key (classescarto) , key (blobid) , key (area) ) ENGINE = 'InnoDB'). Errno: 1005 Answer to my software in this way : Can't create table '.\psd\2010_03_18_blob.frm' (errno: -1) - 11:47:21(569) and after the MYSQL-NT thread goes in crash. The hard-disk is not full. This flag is on: "innodb_file_per_table=1" Then in the directory there is only the 2010_03_18_blob.IDB file: Volume in drive C has no label. Volume Serial Number is 4491-CE96 Directory of C:\Program Files\MySQL\MySQL Server 5.0\data\psd 18/03/2010 12.06 <DIR> . 18/03/2010 12.06 <DIR> .. 06/03/2010 13.26 18.244 2010_03_06_densita.frm 06/03/2010 23.59 100.663.296 2010_03_06_densita.ibd 06/03/2010 23.59 18.244 2010_03_07_densita.frm 07/03/2010 23.59 197.132.288 2010_03_07_densita.ibd 07/03/2010 23.59 18.244 2010_03_08_densita.frm 08/03/2010 23.59 201.326.592 2010_03_08_densita.ibd 08/03/2010 23.59 18.244 2010_03_09_densita.frm 10/03/2010 00.00 184.549.376 2010_03_09_densita.ibd 10/03/2010 00.00 18.244 2010_03_10_densita.frm 11/03/2010 00.08 201.326.592 2010_03_10_densita.ibd 11/03/2010 00.00 18.244 2010_03_11_densita.frm 11/03/2010 23.59 109.051.904 2010_03_11_densita.ibd 11/03/2010 23.59 18.244 2010_03_12_densita.frm 12/03/2010 23.59 205.520.896 2010_03_12_densita.ibd 12/03/2010 23.59 18.244 2010_03_13_densita.frm 13/03/2010 23.59 184.549.376 2010_03_13_densita.ibd 13/03/2010 23.59 18.244 2010_03_14_densita.frm 14/03/2010 17.33 167.772.160 2010_03_14_densita.ibd 15/03/2010 02.17 18.244 2010_03_15_densita.frm 16/03/2010 00.00 121.634.816 2010_03_15_densita.ibd 16/03/2010 19.46 671.744 2010_03_16_blob.ibd 15/03/2010 23.59 18.244 2010_03_16_densita.frm 16/03/2010 19.49 167.772.160 2010_03_16_densita.ibd 17/03/2010 01.30 13.196 2010_03_17_blob.frm 17/03/2010 18.45 491.520 2010_03_17_blob.ibd 17/03/2010 01.29 18.244 2010_03_17_densita.frm 17/03/2010 23.11 192.937.984 2010_03_17_densita.ibd 18/03/2010 08.07 65.536 2010_03_18_blob.ibd 18/03/2010 08.07 65.536 2010_03_18_densita.ibd 22/02/2010 11.49 65 db.opt .... 31 File(s) 2.035.763.965 bytes 2 Dir(s) 26.247.258.112 bytes free Now I try to remove IDB files: Volume in drive C has no label. Volume Serial Number is 4491-CE96 Directory of C:\Program Files\MySQL\MySQL Server 5.0\data\psd 18/03/2010 12.08 <DIR> . 18/03/2010 12.08 <DIR> .. 06/03/2010 13.26 18.244 2010_03_06_densita.frm 06/03/2010 23.59 100.663.296 2010_03_06_densita.ibd 06/03/2010 23.59 18.244 2010_03_07_densita.frm 07/03/2010 23.59 197.132.288 2010_03_07_densita.ibd 07/03/2010 23.59 18.244 2010_03_08_densita.frm 08/03/2010 23.59 201.326.592 2010_03_08_densita.ibd 08/03/2010 23.59 18.244 2010_03_09_densita.frm 10/03/2010 00.00 184.549.376 2010_03_09_densita.ibd 10/03/2010 00.00 18.244 2010_03_10_densita.frm 11/03/2010 00.08 201.326.592 2010_03_10_densita.ibd 11/03/2010 00.00 18.244 2010_03_11_densita.frm 11/03/2010 23.59 109.051.904 2010_03_11_densita.ibd 11/03/2010 23.59 18.244 2010_03_12_densita.frm 12/03/2010 23.59 205.520.896 2010_03_12_densita.ibd 12/03/2010 23.59 18.244 2010_03_13_densita.frm 13/03/2010 23.59 184.549.376 2010_03_13_densita.ibd 13/03/2010 23.59 18.244 2010_03_14_densita.frm 14/03/2010 17.33 167.772.160 2010_03_14_densita.ibd 15/03/2010 02.17 18.244 2010_03_15_densita.frm 16/03/2010 00.00 121.634.816 2010_03_15_densita.ibd 16/03/2010 19.46 671.744 2010_03_16_blob.ibd 15/03/2010 23.59 18.244 2010_03_16_densita.frm 16/03/2010 19.49 167.772.160 2010_03_16_densita.ibd 17/03/2010 01.30 13.196 2010_03_17_blob.frm 17/03/2010 18.45 491.520 2010_03_17_blob.ibd 17/03/2010 01.29 18.244 2010_03_17_densita.frm 17/03/2010 23.11 192.937.984 2010_03_17_densita.ibd 18/03/2010 12.07 523 bug.rar 22/02/2010 11.49 65 db.opt .... 31 File(s) 2.035.635.555 bytes 2 Dir(s) 26.247.966.720 bytes free But nothing change How to repeat: I will attach data and configuration file.