Daevid, --The logfiles are the same size so I assume that's configured right?
They should be. If you copied the file over, mysql isn't going to increase/decrease the size of the file (because it already exists). I suspect that you didn't save the old my.cnf file. The only other question I have is why is the "New" file smaller than the original. innodb doesn't shrink files to the best of my knowledge (or at least, it hasn't for me) -- or did you mean that the top one is the new, and the bottom one is the old.. So, looking a little harder at your files, I bet you tried to start myself against the USB device directly, on the first try, it failed, so you copied the data over to the local disk and you have been trying to recover it since. I say that because the time stamp on the usb (new or old ones) but have July 14th as the dates... I think as others have mentioned, the startup recovery flags might be your best bet. ________________________________________ From: Daevid Vincent [dae...@daevid.com] Sent: Tuesday, July 14, 2009 12:23 PM To: mysql@lists.mysql.com Cc: Gary Smith Subject: RE: Copy 70GB ibdata, etc. and server won't start now > -----Original Message----- > From: Gary Smith [mailto:g...@primeexalia.com] > Sent: Monday, July 13, 2009 8:54 PM > To: Daevid Vincent; mysql@lists.mysql.com > Subject: RE: Copy 70GB ibdata, etc. and server won't start now > > > InnoDB: Your database may be corrupt or you may have copied > the InnoDB > > InnoDB: tablespace but not the InnoDB log files. See > > InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html > > InnoDB: for more information. > > InnoDB: Error: trying to access page number 2144600306 in space 0, > > InnoDB: space name ./ibdata1, > > InnoDB: which is outside the tablespace bounds. > > InnoDB: Byte offset 0, len 16384, i/o type 10. > > InnoDB: If you get this error at mysqld startup, please check that > > InnoDB: your my.cnf matches the ibdata files that you have in the > > InnoDB: MySQL server. > > 090714 1:43:18InnoDB: Assertion failure in thread > 3083368144 in file > > fil0fil.c line 3959 > > InnoDB: We intentionally generate a memory trap. > > InnoDB: Submit a detailed bug report to http://bugs.mysql.com. > > InnoDB: If you get repeated assertion failures or crashes, even > > InnoDB: immediately after the mysqld startup, there may be > > InnoDB: corruption in the InnoDB tablespace. Please refer to > > InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html > > InnoDB: about forcing recovery. > > First thing that comes to mind is a scenario that happened > some time ago when we migrated data from one server to > another in a similar way. Server one had the innodb file set > to 2gb each file (10 files total). New server was set for > 1gb each. It doesn't shrink files so not much was thought > about it at the time but our problem was the innodb table > settings had to match to the letter. We ended up copying the > copy file from the old machine to the new machine (they were > running the same version so it really wasn't a problem. The logfiles are the same size so I assume that's configured right? > I know that you stated you were running Ubuntu, which is > great, but what version of the database did it come from and > what version of the database is it going to? +------+ | Old: | +------+ mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 drwx------ 2 mysql mysql 12288 2009-06-26 21:33 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw---- 1 mysql mysql 72387395584 2009-07-14 19:18 ibdata1 -rw-rw---- 1 mysql mysql 5242880 2009-07-14 19:18 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 2009-07-14 18:30 ib_logfile1 drwxr-xr-x 2 mysql mysql 4096 2008-11-24 23:34 mysql +------+ | New: | +------+ mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 drwx------ 2 mysql mysql 12288 2009-07-14 00:36 agis_core -rw-r--r-- 1 mysql mysql 0 2008-11-24 23:34 debian-5.0.flag -rw-rw---- 1 mysql mysql 70038585344 2009-06-17 04:09 ibdata1 -rw-rw---- 1 mysql mysql 5242880 2009-07-14 01:43 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 2009-06-17 03:22 ib_logfile1 drwxr-xr-x 2 mysql mysql 4096 2009-07-14 00:36 mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
