Ian,

----- Original Message ----- From: "Ian Grant" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 05, 2005 4:47 PM
Subject: Re: InnoDB: Error: tablespace size stored in header is 17024 pages,



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.

hmm... a bug in tar?

...
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

You have to add new data files to the end of the line, not to the start. Please follow the instructions at
http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html


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?

Best regards,

Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to