Can you just put the files back where they were originally? Ordinarily that would be in the path set up in mysql - see SHOW VARIABLES LIKE "datadir"
You do need to have your ibdata* files and ib_logfile* files all in there, assuming you weren't using the file-per-table setup (if you were then I am not sure; haven't tried that one yet myself). I'd shut down the server process, move everything into place, double-check permissions on the files, and then start the mysqld server process back up. Dan On 10/18/06, George-Cristian Bîrzan <[EMAIL PROTECTED]> wrote:
Hello! I'm having some troubles fixing an InnoDB messup, maybe somebody will be able to help me with at least knowing if it's a lost cause... A colleague of mine moved the ib* files around, with MySQL (5.0.15) still running, which didn't really do it justice... The problem might've been made worse by the fact that the server was out of space at the time, which was what he was trying to fix. Now, when starting MySQL with innodb_force_recovery set to 1, I get the errors in http://hephaestus.rdsct.ro/~gcbirzan/mysql.log. So, bottom line, lacking any relevant backups, is there a way to fix this? (Well, I have the .MYD and .MYI from back when the table was MyISAM, but I lack the .frm, and using an older one makes MySQL segfault...) -- George-Cristian Bîrzan -- 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]
