We have replicated this crash over and over just now... Very strange. Yet with the 2.23.30 version, we dont lose the data and dont seem to get corruption. Here is exactly what happened... (This also crashed it in the first place, which lost all our data in the 2.23.28 version) We have a table called user For testing we went to do this insert into the db... which, by the way, was trying to insert into the 17th row in an auto incremented id... This is a Berkely DB file. ERROR 2013: Lost connection to MySQL server during query mysql> insert into user (user_id,user_name,first_name,last_name,display_name,email,notes,password) values (NULL,'testuser','Jason','mCwIl','jason ','[EMAIL PROTECTED]','none','tester'); ERROR 2006: MySQL server has gone away No connection. Trying to reconnect... Connection id: 1 You could sit and do this over and over and over. But, the connection would come right back and no data was lost. So, I actually tried a different query next: insert into user values (NULL,'tester','jason','jason','jason mcwilliams','tridog','','[EMAIL PROTECTED]','','','','','','','','','','','','','','','','','','','',''); or somthing simlar which produced: Query OK, 1 row affected (0.02 sec) So, I thought it might be the format of the insert... so then I try the first insert again: insert into user (user_id,user_name,first_name,last_name,display_name,email,notes,password) values (NULL,'testuser','Jason','mCwIl','jason ','[EMAIL PROTECTED]','none','tester'); Query OK, 1 row affected (0.02 sec) I havn't had another error since? It was like it could not insert that style of insert into that particular row, once it got passed that... it is fine. I would think we could reproduce this by dropping the database recreating it, and redoing the create statements (just like we had to do to recover)... If anyone from mysql is interested in trying to reproduce this, let me know. -- Jason McWilliams Tridog Interactive, Inc. 303-415-2538 Jason McWilliams wrote: > > Well, we upgraded to 2.23.30 and tried to bring it up with the same > seemingly corrupt > datafiles. It tried to do a recovery (saw this in the error log), but > died when > it was looking for database directories that had long ago been deleted. > It was like > it was making its way through the entire db transaction log. > > We ended dropping the entire database and going to our most recent > mysqldump. We just > have to hope that the .30 version fixed this corrupted file thing when > mysql crashes. > > If anyone else has knowledge about this, it would be greatly > appreciated. Or if anyone > knows what type of fixes were made with Berkely db files from the .28 to > .30 release. > > -- > Jason McWilliams > Tridog Interactive, Inc. > 303-415-2538 > > "Mehalick, Richard RE SSI-GRAX" wrote: > > > > The MySQL team recommended upgrading to 3.23.29 gamma, especially if using > > Berkeley DB. > > > > ----------------------------------------- > > / Rick Mehalick Senior Consultant > > / Shell Services International SSI-GPAX > > / Phone: 281-544-5092(WCK) > > / Fax: 281-544-2646(WCK) > > / email: [EMAIL PROTECTED] > > ----------------------------------------- > > > > -----Original Message----- > > From: Jason McWilliams [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 11, 2001 4:23 PM > > To: [EMAIL PROTECTED] > > Subject: 3.23.28-gamma Crash and data loss > > > > We have been using 3.23.28-gamma with berkely db files so we can use > > transactions. > > > > Platform: BSDI 4.1 > > > > Everything was rolling along fine when we ran into this while doing some > > simple command line stuff... > > > > It gives me the error that mysql has gone away... lost connection... > > Something I have seen before. > > > > It simply regains a connection and everything seemed fine... > > > > Yet, we lost all data in all .db files. The index information in the > > .frm files were fine. > > The regular .MYD and .MYI files were all ok as well. > > > > The strange thing is that the .db file sizes were still pretty large. > > Yet, when doing queries, it just > > says the rows are gone. You can insert etc... > > > > For instance, I did an insert on an auto_encrement field and it gave an > > id of 1... there were many rows before them mysql crash... > > > > Has anyone else seen this type of problem after a mysql crash with the > > Berkely db files? > > > > -- > > Jason McWilliams > > Tridog Interactive, Inc. > > 303-415-2538 > > ------------------------------------------------------------------------ > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) >
--------------------------------------------------------------------- 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
