Richard,
----- Original Message ----- From: ""Richard F. Rebel"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 12, 2005 8:07 PM
Subject: InnoDB files corrupt after copy to another disk???
--=-55yKssoEPEmA1J8GXefY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable
Hello,
I am trying to copy my innodb table spaces to a new array. When I copy the files to their new location and start mysql-max with the new configuration, invariably I get the following after I attempt to actually connect to a database with the command line client:
mysqld-max process hanging, pid 20607 - killed 050112 12:58:38 mysqld restarted /usr/bin/mysqld_safe: line 1: 23476 Killed nohup /usr/sbin/mysqld-max --defaults-file=3D/idb/d1/mysql/logdata/my.cnf --basedir=3D/ --datadir=3D/idb/d1/mysql/logdata/data/ --user=3Dmysql --pid-file=3D/idb/d1/mysql/logdata/mysql.logdata.pid --skip-locking --port=3D3301 --socket=3D/tmp/mysql.logdata.sock.idb/idb/d1/mysql/logdata/log/mysql.logdata.err.log 2>&1050112 12:58:38 mysqld ended
InnoDB: Error: page n:o stored in the page read in is 1333252, should be 1589252!
the page number is exactly 4000 MB too small. Maybe you have ibdata files in the wrong order, or have copied an ibdata file over another, or some ibdata files are mentioned more than once in the innodb_data_file_path?
...
Richard F. Rebel
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]
