Marten,
- Original Message -
From: "Marten Lehmann" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, March 29, 2006 7:52 PM
Subject: Re: innodb errors on startup
Well,
ok, we need to stress this more in the manual. A few users have
misunders
Well,
ok, we need to stress this more in the manual. A few users have
misunderstood that ibdata files would no longer be needed if one uses
innodb_file_per_table.
ib_logfiles are always needed. How else can InnoDB recover after a crash.
but how can I repair my existing ib-files so that the
Marten,
Marten Lehmann wrote:
Hello Heikki,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
the complete log is about 50 mb, since a lot of errors occur.
I am interested in what caused the very first crash in the server. Now
your
database seems to be seriously corr
Hello Heikki,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
the complete log is about 50 mb, since a lot of errors occur.
I am interested in what caused the very first crash in the server. Now your
database seems to be seriously corrupt, since the log sequence numb
Marten,
I replied today to your earlier email with the message pasted below.
Regards,
Heikki
Marten,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
I am interested in what caused the very first crash in the server. Now your
database seems to be seriously c
Margrit,
your disk or file system is probably broken:
> InnoDB: Fatal error: cannot read from file. OS error number 17.
17 EEXIST File exists
The error number does not make sense in a file read. Strange.
You cannot remove ib_logfiles from an InnoDB installation. They are as
important as ibdata
Margrit,
fix the problem that leads to OS error number 17.
What does perror tell you about it?
Regards,
Frank.
Margrit Lottmann schrieb:
>
> Following errors we've got by restarting mysqld
>
> 031114 10:26:51 mysqld started
> InnoDB: Fatal error: cannot read from file. OS error number 1
Shane,
it is not an InnoDB error message. InnoDB messages are always prefixed with
InnoDB:
The error means that there is an inconsistent row in the db.MYD system table
of MySQL.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and row level locking for M
