Dear Heikki Many thanks for your reply.
On Mon, 3 Jan 2005 20:41:22 +0200 "Heikki Tuuri" <[EMAIL PROTECTED]> wrote: > are you sure that you copied the complete ibdata1 file to the new > place? It is strange how 7 MB can be missing from the file end. I have just checked the tar file I used to do the transfer and sure enough, the file length is right there, but not in my database directory. Obviously I didn't notice any error when I unpacked it, but it is definitely short now. So that (partly) explains what went wrong ... however we have new data in the database now so it is too late to go back tho that copy. > What does the old .err log contain? Any message about disk space > running out? > > The error below probably has not corrupted your tablespace. Best to > run CHECK TABLE on some of your tables, though. I did that on all tables and they all show they are OK. > When ibdata files are created, they are initially written full of > zeros. You can probably fix the error by using another mysqld > installation (or any method that makes a 7 MB zero-filled file) to > create a new ibdata2 file that is 7 MB in size, and add that to the > tablespace. Look from > http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html > how to edit my.cnf then. Thanks. This is what I did: First I created ibdata2 with the command dd if=/dev/zero bs=1M count=7 of=ibdata2 Then I added it to the start of the tablespace path in my.cnf by changing innodb_data_file_path = ibdata1:10M:autoextend to innodb_data_file_path = ibdata2:7M;ibdata1:10M:autoextend Then I shut down: 050105 14:25:57 [Note] /local/own-1/rt/rt-3.2.2/libexec/mysqld: Normal shutdown 050105 14:25:57 InnoDB: Starting shutdown... 050105 14:26:01 InnoDB: Shutdown completed; log sequence number 0 407778847 050105 14:26:01 [Note] /local/own-1/rt/rt-3.2.2/libexec/mysqld: Shutdown complete 050105 14:26:01 mysqld ended ... and restarted MySQL but I got an error: 050105 14:26:04 mysqld started 050105 14:26:05 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050105 14:26:05 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 407778847. InnoDB: Doing recovery: scanned up to log sequence number 0 407778847 InnoDB: Page directory corruption: supremum not pointed to followed by a page dump and a stack trace. I removed the entry for the new file in the data file path and it has started as it did before. Have I misunderstood your instructions? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
