Cloned machine mysql startup problem with innodb

[Paul W]

For backup purposes I have what amounts 
to a complete clone of a live server. 
During the process of copying 
everything, the MySQL data was copied 
over in its entirety. My problem is that 
the mysqld won't start now on this 
second machine. I don't need the 
databases to be preserved here (intend 
to rebuild them later then dump data 
into them). Therefore I can delete the 
database files themselves and start 
again if need be, but I'm not sure what 
would be a correct way to do this with 
the innodb error shown below. Somebody 
know if it's safe to delete most things 
from /var/lib/mysql? Could I just delete 
libdata1?

As to the line saying I should edit 
innodb_data_file_path back to what it 
was - I have no idea what it was  :-(

I'm after the simplest way to get it 
started, the rest is easy.

from the startup errors:
InnoDB: Error: data file 
/var/lib/mysql/ibdata1 is of a different 
size
InnoDB: 6656 pages (rounded down to MB)
InnoDB: than specified in the .cnf file 
128000 pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data 
files, and it failed here,
InnoDB: you should now edit 
innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the 
new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB 
only wrote those files full of
InnoDB: zeros, but did not yet use them 
in any way. But be careful: do not
InnoDB: remove old data files which 
contain your precious data!
041019 13:05:25  Can't init databases
041019 13:05:25  Aborting

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