Re: Table corruption at MySQL 4.0.0 shutdown ?
Hi! > "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes: Sinisa> Fournier Jocelyn [Presence-PC] writes: >> Hi, >> >> I noticed an annoying behaviour with MySQL 4.0.0. >> I have 11 tables with a lot of rows (about 1 Million and more) which are constantly >updated by a php script. >> It seems after a shutdown of mysql (mysqladmin -uroot -p shutdown) and a restart, >some tables are corrupted (and not the same, it randomly occurs), and I have to run a >myisamchk to repair them. >> >> Here is the structure of the table : >> >> >> CREATE TABLE searchhardwarefr9 ( >> mot varchar(30) NOT NULL, >> topic mediumint(8) unsigned DEFAULT '0' NOT NULL, >> date date DEFAULT '-00-00' NOT NULL, >> pseudo varchar(35) NOT NULL, >> numreponse int(10) unsigned DEFAULT '0' NOT NULL, >> PRIMARY KEY (mot, pseudo, date, numreponse, topic), >> KEY pseudo (pseudo, date, numreponse, topic), >> KEY numreponse (numreponse, topic), >> KEY topic (topic) >> ); Apart from the new key-cache code and batch insert code, the MyISAM code is identical in MySQL 3.23 and 4.0 Could you try to follow the instruction at http://www.mysql.com/doc/R/e/Reproduceable_test_case.html to try to make a test case of this? Regards, Monty -- For technical support contracts, goto https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Michael Widenius <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, CTO /_/ /_/\_, /___/\___\_\___/ Helsinki, Finland <___/ 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: Table corruption at MySQL 4.0.0 shutdown ?
Fournier Jocelyn [Presence-PC] writes: > Hi, > > I noticed an annoying behaviour with MySQL 4.0.0. > I have 11 tables with a lot of rows (about 1 Million and more) which are constantly >updated by a php script. > It seems after a shutdown of mysql (mysqladmin -uroot -p shutdown) and a restart, >some tables are corrupted (and not the same, it randomly occurs), and I have to run a >myisamchk to repair them. > > Here is the structure of the table : > > > CREATE TABLE searchhardwarefr9 ( >mot varchar(30) NOT NULL, >topic mediumint(8) unsigned DEFAULT '0' NOT NULL, >date date DEFAULT '-00-00' NOT NULL, >pseudo varchar(35) NOT NULL, >numreponse int(10) unsigned DEFAULT '0' NOT NULL, >PRIMARY KEY (mot, pseudo, date, numreponse, topic), >KEY pseudo (pseudo, date, numreponse, topic), >KEY numreponse (numreponse, topic), >KEY topic (topic) > ); > > -=[root@s15]=(/usr/local/var/Hardwarefr)# myisamchk -o searchhardwarefr9.MYI > <(17:31:25) > - recovering (with keycache) MyISAM-table 'searchhardwarefr9.MYI' > Data records: 977549 > Duplicate key 1 for record at 30977704 against new record at 30946580 > Duplicate key 1 for record at 30977736 against new record at 30946612 > Duplicate key 1 for record at 30977768 against new record at 30946644 > Duplicate key 1 for record at 30977796 against new record at 30946672 > Duplicate key 1 for record at 30977828 against new record at 30946704 > Duplicate key 1 for record at 30977860 against new record at 30946736 > Duplicate key 1 for record at 30977896 against new record at 30946772 > Duplicate key 1 for record at 30977928 against new record at 30946804 > Duplicate key 1 for record at 30977960 against new record at 30946836 > Duplicate key 1 for record at 30977992 against new record at 30946868 > Duplicate key 1 for record at 30978024 against new record at 30946900 > Data records: 977538 > myisamchk: warning: 11 records have been removed > > Any idea ? (hardware related or mysql related ?) > > Thank you :) > > Jocelyn Fournier > Presence-PC > As you know very well, we would truly need a repeatable test case. We are very keen of fixing our 4.0 bugs, and this could be one. It could be hardware too, but how could we know ? -- 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
Table corruption at MySQL 4.0.0 shutdown ?
Hi, I noticed an annoying behaviour with MySQL 4.0.0. I have 11 tables with a lot of rows (about 1 Million and more) which are constantly updated by a php script. It seems after a shutdown of mysql (mysqladmin -uroot -p shutdown) and a restart, some tables are corrupted (and not the same, it randomly occurs), and I have to run a myisamchk to repair them. Here is the structure of the table : CREATE TABLE searchhardwarefr9 ( mot varchar(30) NOT NULL, topic mediumint(8) unsigned DEFAULT '0' NOT NULL, date date DEFAULT '-00-00' NOT NULL, pseudo varchar(35) NOT NULL, numreponse int(10) unsigned DEFAULT '0' NOT NULL, PRIMARY KEY (mot, pseudo, date, numreponse, topic), KEY pseudo (pseudo, date, numreponse, topic), KEY numreponse (numreponse, topic), KEY topic (topic) ); -=[root@s15]=(/usr/local/var/Hardwarefr)# myisamchk -o searchhardwarefr9.MYI <(17:31:25) - recovering (with keycache) MyISAM-table 'searchhardwarefr9.MYI' Data records: 977549 Duplicate key 1 for record at 30977704 against new record at 30946580 Duplicate key 1 for record at 30977736 against new record at 30946612 Duplicate key 1 for record at 30977768 against new record at 30946644 Duplicate key 1 for record at 30977796 against new record at 30946672 Duplicate key 1 for record at 30977828 against new record at 30946704 Duplicate key 1 for record at 30977860 against new record at 30946736 Duplicate key 1 for record at 30977896 against new record at 30946772 Duplicate key 1 for record at 30977928 against new record at 30946804 Duplicate key 1 for record at 30977960 against new record at 30946836 Duplicate key 1 for record at 30977992 against new record at 30946868 Duplicate key 1 for record at 30978024 against new record at 30946900 Data records: 977538 myisamchk: warning: 11 records have been removed Any idea ? (hardware related or mysql related ?) Thank you :) Jocelyn Fournier Presence-PC
