hi,
I had already meet this situation: after I unpluggin the power cable, then
start OS(redhat9.0, ext3 fs), start mysql, but innodb recovery was failed!
but, I also test this case on another os(RHEL4,ext3 fs), there is no any
problem.
I think there maybe different to handle filesys
On 3/11/07, Jean-Sebastien Pilon <[EMAIL PROTECTED]> wrote:
I am running a mysql database server and we experienced a power failure.
The mysql server does not want to restart because innodb is corrupted.
Version info:
Mysql version 4.1.11-Debian_4sarge7-log
Debian sarge
Reiserfs filesystem
Wha
]: InnoDB: If you get repeated
assertion failures or crashes, even
Mar 10 17:57:22 db01-mtl mysqld[3582]: InnoDB: immediately after the
mysqld startup, there may be
Mar 10 17:57:22 db01-mtl mysqld[3582]: InnoDB: corruption in the InnoDB
tablespace. Please refer to
Mar 10 17:57:22 db01-mtl mysqld[3582
- Original Message -
From: ""Andrew Brockert"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Sunday, May 21, 2006 4:59 AM
Subject: InnoDB corruption and crash on Windows 2000
--=_Part_127305_14374727.1148176365800
Content-Type: text/plain; charset
I am running MySQL with hMailServer on Windows 2000 Pro. I was forced to
hard reboot the machine this morning, and this is now the result of running
mysqld-nt with --console:
060520 21:38:23 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Startin
Bruce Dembecki wrote:
At the 2004 Users Conference in Orlando in April there were two sessions on
optimizing MySQL hosted by a MySQL staffer who's name eludes me for the
moment.
Peter Zaitsev I believe. He did some InnoDB performance tuning sessions.
He told the assembled masses that in benchmark
Hi Bruce,
On Dec 28, 2004, at 2:38 PM, Bruce Dembecki wrote:
As a person in the process of migrating from 4.0 to 4.1 and having
already
scheduled the downtime with my clients for this Friday morning, and
having
to do a full dump and import already as part of the migration process
I'd
like to kno
L and contributing to it's development.
Best Regards, Bruce
On 1/6/05 7:38 AM, "Ken Menzel" <[EMAIL PROTECTED]> wrote:
> Hi Bruce
>
>
> - Original Message -
> From: "Bruce Dembecki" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday
Hi Bruce
- Original Message -
From: "Bruce Dembecki" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 30, 2004 2:51 AM
Subject: Re: Fixing "the worst InnoDB corruption bug in 3 years" -
when
As a side note with demonstrated performance increases when using
t; <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, December 30, 2004 9:51 AM
Subject: Re: Fixing "the worst InnoDB corruption bug in 3 years" - when
Thanks Heikki, I understand the bug, and I know you fixed it, for which I
a=
m
very pleased, as always problems
sorry
--
-- -- -- --
Sayusi Ando
-- -- -- --
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
e people using it?
Best Regards, Bruce
On 12/29/04 10:22 PM, Heikki Tuuri wrote:
> Bruce,
>
> It is the bug "innodb_file_per_table corrupts secondary indexes".
>
> I fixed it with several changesets on Sunday:
>
> http://lists.mysql.com/internals
>
> Thus, i
Bruce,
it is the bug "innodb_file_per_table corrupts secondary indexes".
I fixed it with several changesets on Sunday:
http://lists.mysql.com/internals
Thus, it is fixed in the current 4.1 bk tree.
This is indeed the worst InnoDB corruption bug since the BLOB update bug of
s
#7496) for more information and workarounds.
Following the link to Bug 7496 (http://bugs.mysql.com/bug.php?id=7496) we
are told two important things:
1. This is the worst InnoDB corruption bug in 3 years.
2. Will be fixed in 4.1.9.
So thanks to Heikki for finding and fixing this.
So now to the qu
Carlos,
- Original Message -
From: "Carlos Augusto" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, November 26, 2004 8:46 PM
Subject: Re: Innodb Corruption with error logs now.
Well Heikki i don=B4t have those .frm and i don=B4t know the &#
ables
> http://www.innodb.com/order.php
>
> - Alkuperäinen viesti -
> Lähettäjä: "Carlos Augusto" <[EMAIL PROTECTED]>
> Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Lähetetty: Friday, November 26, 2004
EMAIL PROTECTED]>
Lähetetty: Friday, November 26, 2004 6:11 PM
Aihe: Re: Innodb Corruption with error logs now.
Well look what i did: I changed innodb_log_file_size as you asked me
for 5M and then i tryed to start mysqld again then i it doesnt run.
And the output at err.log was this one:
I will reme
modified pages from the buffer pool...
> 041125 22:02:34 InnoDB: Started; log sequence number 0 49164
> 041125 22:02:34 [Warning] mysql.user table is not updated to new password
> format
> ; Disabling new password usage until mysql_fix_privilege_tables is run
> ./mysqld: ready for conne
distr
ibution
- Original Message -
From: "Carlos Augusto" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 25, 2004 8:59 PM
Subject: Re: Innodb Corruption with error logs now.
ib_logfile is different from ibdata1.=20
Just because i get the databa
Lähettäjä: "Carlos Augusto" <[EMAIL PROTECTED]>
> Vastaanottaja: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Lähetetty: Thursday, November 25, 2004 8:01 PM
> Aihe: Innodb Corruption with error logs now.
>
>
>
>
> Well, let me begin again..
>
;; <[EMAIL PROTECTED]>
Lähetetty: Thursday, November 25, 2004 8:01 PM
Aihe: Innodb Corruption with error logs now.
Well, let me begin again..
I´m new in a corporation and my jobs is deal with mysql.
We had, running mysqld 4.1.7 and using Innodb for a database of
4.7GB~. But some time inserting
Well, let me begin again..
I´m new in a corporation and my jobs is deal with mysql.
We had, running mysqld 4.1.7 and using Innodb for a database of
4.7GB~. But some time inserting data into it, the server crashed.
So i get the server do analyze it.
When i get to the server the mysqld(config-fil
We am having constant index corruption problems since moving
from 4.0.17 to 4.1.3. All tables are InnoDB and we're using
the file-per-table setting on Solaris9.
Every couple days another few tables will show up corrupt
and queries start missing things. The database has never
gone down, there hav
Hi,
I’m using Win98 with mysql 4.0.1-alpha-max-debug. My main
database has only InnoDB tables and, I don’t know how, some tables were
corrupted. My problem is using the CHECK statement I can find where the
corruptions are but I can’t repair them with REPAIR (error message: table
han
24 matches
Mail list logo
