Sveta Smirnova at Mysql just confirmed this bug in 5.5.13:
http://bugs.mysql.com/45670
On Wed, Jun 15, 2011 at 5:38 PM, Claudio Nanni wrote:
> No worries!
>
> I think I would have figured that out!
>
> I'll feedback you tomorrow.
>
> Thanks again
>
> Claudio
>
> 2011/6/15 Hank
>
>> Oops... big
No worries!
I think I would have figured that out!
I'll feedback you tomorrow.
Thanks again
Claudio
2011/6/15 Hank
> Oops... big typo in above steps... add the following line:
>
> replicate-ignore-table=db.log
>
> to the SLAVE my.cnf, and restart the SLAVE server.
>
> The master does not ne
Oops... big typo in above steps... add the following line:
replicate-ignore-table=db.log
to the SLAVE my.cnf, and restart the SLAVE server.
The master does not need to be restarted or changed. Just the SLAVE.
Sorry about that.
-Hank Eskin
On Wed, Jun 15, 2011 at 5:19 PM, Claudio Nanni wro
Great investigation Hank,
congratulations.
I will try this tomorrow morning(11:20pm now) and let you know if I can
reproduce it on my environments.
Thanks!
Claudio
2011/6/15 Hank
> Two additional notes:
>
> 1. Using the "replicate-wild-ignore-table" option in my.cnf produces the
> same res
Two additional notes:
1. Using the "replicate-wild-ignore-table" option in my.cnf produces the
same results.
2. If the my.cnf "replicate-ignore-table=db.log" setting on the master is
removed and mysql restarted so "db.log" is no longer ignored in replication,
this bug goes away and correct res
This is a follow-up to my previous post. I have been narrowing down what is
causing this bug. It is a timing issue of a replication ignored table with
an auto-increment primary key values leaking over into a non-ignored table
with inserts immediately after the ignore table has had rows inserted.
s identical hardware and only a slightly upgraded distro (but also
> running 5.1.23-rc), I get a glibc malloc(): memory corruption: *** error,
> which traces back to the mysql_real_connect() call. I ran ldd -v on the
> binary on both machines and there are some differences, but they do
ng
5.1.23-rc), I get a glibc malloc(): memory corruption: *** error, which traces
back to the mysql_real_connect() call. I ran ldd -v on the binary on both
machines and there are some differences, but they don't look important. I have
run this binary on other machines before with no issues.
istro (but also running
5.1.23-rc), I get a glibc malloc(): memory corruption: *** error, which traces
back to the mysql_real_connect() call. I ran ldd -v on the binary on both
machines and there are some differences, but they don't look important. I have
run this binary on other machines b
Hi,
Have you tried changing the date format like
delete from TelecomAccountPosting where LocID=19014 and InvDate='2008-01-15';
I know it shouldn't matter but I have had similar issues due to the date
format.
Also are you sure there are 3773 records matching this criteria - according to
your t
On Tue, 2008-01-22 at 11:23 +1100, Chris wrote:
> > Why is it saying 'Impossible WHERE noticed after reading const tables'?
>
> http://dev.mysql.com/doc/refman/4.1/en/explain.html
> MySQL has read all const (and system) tables and notice that the WHERE
> clause is always false.
>
> ie - no rows
Daniel Kasak wrote:
Greetings.
I have a script which seems to be bringing our server to its knees.
I've isolated one query which is doing it:
delete from TelecomAccountPosting where LocID = 19014 and InvDate =
'20080115';
I have an index which covers both LocID and InvDate:
CREATE TABLE `Tel
Greetings.
I have a script which seems to be bringing our server to its knees.
I've isolated one query which is doing it:
delete from TelecomAccountPosting where LocID = 19014 and InvDate =
'20080115';
I have an index which covers both LocID and InvDate:
CREATE TABLE `TelecomAccountPosting` (
hrieb:
Hey guys,
First of all: I have tried to post this Issue on forums.mysql.com,
but the Topic doesn't appear in the Forum. When I try to post again,
it tells me that it's a duplicate?!?!
Now the real problem:
I have MySQL set up on two Servers with 7000 Users each and about
the
From: Frank Bottone [mailto:[EMAIL PROTECTED]
Sent: Monday, October 08, 2007 3:49 PM
To: Baron Schwartz
Cc: mysql@lists.mysql.com
Subject: Re: Problem with repeated replication corruption - Could not
parse relay log event entry
Baron,
Thanks for the quick response. I do have the binlogs still
able-checksum. Your data
could be fine, but it might also be different on the slave. But
there's no need to worry about it until you prove it:
http://mysqltoolkit.sourceforge.net/
Your corruption in the relay logs could be caused by any number of
things -- bad network, bad hardware,
er, you might be OK.
You might want to take a look at mysql-table-checksum. Your data could
be fine, but it might also be different on the slave. But there's no
need to worry about it until you prove it:
http://mysqltoolkit.sourceforge.net/
Your corruption in the relay logs cou
I've been having trouble with my master/slave server - recently I was
having a few repeated issues where the mysql slave would stop due to
"invalid sql syntax", but the queries executed fine on the master. I
would have to manually dig through the logs and then find the query to
manually execute
lem:
I have MySQL set up on two Servers with 7000 Users each and about the
same amount of databases.
Since two days ago, there is corruption going on in many databases.
And MySQL crashes every other hour or so.
Last night I updated from 5.0.32 to 5.0.45, but the problem is still
there.
Here is
and about the
same amount of databases.
Since two days ago, there is corruption going on in many databases.
And MySQL crashes every other hour or so.
Last night I updated from 5.0.32 to 5.0.45, but the problem is still
there.
Here is what I see in syslog:
Oct 7 11:02:53 h1314631 mysqld[32
amount of databases.
Since two days ago, there is corruption going on in many databases. And
MySQL crashes every other hour or so.
Last night I updated from 5.0.32 to 5.0.45, but the problem is still there.
Here is what I see in syslog:
Oct 7 11:02:53 h1314631 mysqld[32490]: 071007 11:02:53 [ER
ing on top of drbd.
> >
> > Also, I have been seeing regular corruption of a mysql database,
> > which runs on top of drbd, and when I reported this as a bug since I
> > also recently upgraded mysql versions, they question whether drbd
> > could be responsible!
>
> Se
I failed over the server and ran a short backup and there were no
"didn't compare" errors where on the first server, they are there
pretty reliably. I guess this confirms some hardware on the first
server is flipping bits. Essentially, users could have any number of
munged files (most files are
I guess I will watch it closely for now and if it trips up again
failover to the drbd peer and see what happens there. I suppose I
could even deattach the local disks and have it run using the peer
over the wire. That should eliminate the local I/O subsystem.
It's kind of scary there is no en
Hi Maurice,
If you're running into corruption both in ext3 metadata and in MySQL
data, it is certainly not he fault of MySQL as you're likely aware.
I am hoping they are not related. The problems with MySQL surfaced
almost immediately after upgrading to 5.0.x.
It's possibl
Hi Maurice,
If you're running into corruption both in ext3 metadata and in MySQL
data, it is certainly not he fault of MySQL as you're likely aware.
I am hoping they are not related. The problems with MySQL surfaced
almost immediately after upgrading to 5.0.x.
[details deleted
two
instances where a bit on disk apparently flipped spontaneously in the
ext3 metadata on volumes running on top of drbd.
Also, I have been seeing regular corruption of a mysql database,
which runs on top of drbd, and when I reported this as a bug since I
also recently upgraded mysql versions
Hi Maurice,
If you're running into corruption both in ext3 metadata and in MySQL
data, it is certainly not he fault of MySQL as you're likely aware.
There are absolutely many places where corruption could occur between
MySQL and the physical bits on disk. The corruption you'
On Sep 17, 2007 13:31 -0400, Maurice Volaski wrote:
In using drbd 8.0.5 recently, I have come across at least two
instances where a bit on disk apparently flipped spontaneously in the
ext3 metadata on volumes running on top of drbd.
Also, I have been seeing regular corruption of a mysql
In using drbd 8.0.5 recently, I have come across at least two
instances where a bit on disk apparently flipped spontaneously in the
ext3 metadata on volumes running on top of drbd.
Also, I have been seeing regular corruption of a mysql database,
which runs on top of drbd, and when I reported
this
version of MySQL?
Here's the output of the crash
---
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 533.
InnoDB: You may have to recover from a backup.
070827 3:10:04 InnoDB: Page dump in ascii and hex (16384 bytes):
Hi all,
Starting Wednesday night, we observed several weird errors indicative
of data corruption shortly before a CPU spike and complete crash on
our master db server (opera.oursite.com). opera.oursite.com had
crashed twice with signal 11 in recent weeks, but we had never
observed any data
Thank you for your replies. I attempted to restore again and most
oddly, mysql complained that it couldn't restore to a particular
table because it wasn't in the database, which, of course, it had to
be because the restore itself had just recreated it. So I blew away
the entire mysql directory
> disk is flipping a bit. Or could I be running into a bug in this
> > version of MySQL?
> >
> > Here's the output of the crash
> > ---
> > InnoDB: Database page corruption on disk or a failed
> > InnoDB: file read o
ils seem to be trying to
> suggest some other aspect of the operating system, even the memory or
> disk is flipping a bit. Or could I be running into a bug in this
> version of MySQL?
>
> Here's the output of the crash
> ---
> InnoDB: Database page
page corruption on disk or a failed
InnoDB: file read of page 533.
InnoDB: You may have to recover from a backup.
070827 3:10:04 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
[dump itself deleted for brevity]
;InnoDB: End of page dump
070827 3:10:04 InnoDB: Page checksum 6465
I just changed back to the 'order by id LIMIT 5000' and I have not seen
further
corruption.
I also wanted to mention the other details about the system:
The system is running Linux 2.6.16.21-0.8-smp (SLES10)
mysql-5.0.18-20.5
And I do grant that we probably need to change the
I am getting table corruption on one machine that I was testing a change
to get better performance.
This is using the C API to connect to the database. With the delete
without
the sort by id, I started getting the database key corruption. There
were about
2.6 million rows matched to be
Hi,
Pls try altering the engine type from 'MyISAM' to 'InnoDB'
mysql > alter table `tablename` ENGINE='InnoDB';
Just try out. I'm not sure. But there are issues over 'MyISAM' engine' and
table corruption. Pls look into the link
ht
hello
I am still facing the same problem..
MyISAM table corruptionI am getting following errors
mysql> use DB1;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> check table t
ed somehow to re-run a REPAIR to
see the table finally fixed.
MYSQL docs state for possible reasons for corruption:
[quote] 1- The mysqld process being killed in the middle of a write.
2- Unexpected shutdown of the computer (for example, if the computer is
turned off).
3- A hardware error such as
re-run a REPAIR to
see the table finally fixed.
MYSQL docs state for possible reasons for corruption:
[quote] 1- The mysqld process being killed in the middle of a write.
2- Unexpected shutdown of the computer (for example, if the computer is
turned off).
3- A hardware error such as faulty memory/
vent of a crash.
- Original Message -
From: "tim h" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 22, 2007 2:56 PM
Subject: corruption in db. myisam bad? innodb good?
hi. database is myisam, 5.8Gb, 7mil records.
recently had some corruption i think due to mysqld service
hi. database is myisam, 5.8Gb, 7mil records.
recently had some corruption i think due to mysqld service failure.
10 tabes were crashed.
question --
how can i prevent or minimize this?
Will switching to innodb help?
Will converting all my queries to transactions help?
thanks.
--
Tim H
Berkeley
-
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Frequently-MyISAM-TABLE-corruption.Pls-help-tf3715472.html#a10412877
Sen
; Gerald L. Clark
> Supplier Systems Corporation
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/
Nilnandan wrote:
Hello all,
I have one server which has mysql 5.0.27 installed. There is one table named
table1.
that table has 122000 records..It has 114 fields and 22 indexes.
Now this table always been corrupt. I have try to found the solution but i
couldn't.
Pls help me ASAP. I have used
this message in context:
http://www.nabble.com/Frequently-MyISAM-TABLE-corruption.Pls-help-tf3715472.html#a10393479
Sent from the MySQL - General mailing list archive at Nabble.com.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hello
I send you this message from the Mediawiki mailing list.
It explains clearly that mysqldump has an incorrect behavior which may
lead to data destruction (I got this problem)
Could you please do something to fix it ?
Thanks
Francois Colonna
-BEGIN of MESSAGE-
Sylvain Machefert
<[EMAIL PROTECTED]> wrote:
Sorry it is */*.MYI instead of */*.MYD
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 12:02 PM
> To: Jean-Sebastien Pilon
> Cc: mysql@lists.mysql.com
> Subject: Re: database corruption ? h
Sorry it is */*.MYI instead of */*.MYD
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 12:02 PM
> To: Jean-Sebastien Pilon
> Cc: mysql@lists.mysql.com
> Subject: Re: database corruption ? how to fix ?
>
>
March 22, 2007 8:41 AM
> To: mysql@lists.mysql.com
> Subject: database corruption ? how to fix ?
>
> hi
> when i try and do a mysqldump of the databases it exites with
> this error
>
> [EMAIL PROTECTED] diaendomet]# mysqldump -ucojjohealth -p --all-databases >
> al
t; To: mysql@lists.mysql.com
> Subject: database corruption ? how to fix ?
>
> hi
> when i try and do a mysqldump of the databases it exites with
> this error
>
> [EMAIL PROTECTED] diaendomet]# mysqldump -ucojjohealth -p --all-databases >
> alldatabases.sql
> Enter password:
>
hi
when i try and do a mysqldump of the databases it exites with this error
[EMAIL PROTECTED] diaendomet]# mysqldump -ucojjohealth -p --all-databases >
alldatabases.sql
Enter password:
mysqldump: Got error: 29: File '../diaendomet/users.MYD' not found
(Errcode: 2) when using LOCK TABLES
so i ran
tried:
>
> - Ran reiserfsck to fix corrupted file system. It fixed some problems,
> now says no corruption.
> - Restarted mysql with no success
> - Restarted mysql with innodb_force_recovery = 4 option, with no success
> - Restarted mysql with innodb_force_recovery = 6 option, mys
system
What I have tried:
- Ran reiserfsck to fix corrupted file system. It fixed some problems,
now says no corruption.
- Restarted mysql with no success
- Restarted mysql with innodb_force_recovery = 4 option, with no success
- Restarted mysql with innodb_force_recovery = 6 option, mysql start
file system. It fixed some problems,
now says no corruption.
- Restarted mysql with no success
- Restarted mysql with innodb_force_recovery = 4 option, with no success
- Restarted mysql with innodb_force_recovery = 6 option, mysql starts,
but cannot access any data in my different schemas/tables
Dear Friends:
since 2 weeks ago the mysql is stoping sudenly, and into the error log
is as lines below, "Database page corruption on disk or a failed" ,
"file read of page 34",
how I can know what table is in page 34 ?
I've used mysqlcheck, without any result, all
Andrew,
a possible reason for the corruption is that you have enabled write caching
in the disk controller or in the disk, but those caches are not
battery-backed. Then a hard reboot may destroy the contents, and the
database becomes corrupt.
What kind of hardware are you using? Do you have
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
tables into database
query> UNLOCK TABLES;
Atle
-
Flying Crocodile Inc, Unix Systems Administrator
On Tue, 7 Mar 2006, Michael Jeung wrote:
> Hi Folks,
>
> We've got a Single Master/Multiple Slave environment.
> Recently, we had some corruption on one of the slaves and I had to
e to the
> > corrupt
> > one might prove to be an elegant technique
> >
> > Kishore Jalleda
> >
> > On 3/7/06, Michael Jeung <[EMAIL PROTECTED]> wrote:
> >>
> >> Hi Folks,
> >>
> >> We've got a Single Master/Multiple Sla
ichael Jeung <[EMAIL PROTECTED]> wrote:
Hi Folks,
We've got a Single Master/Multiple Slave environment.
Recently, we had some corruption on one of the slaves and I had to
repair the affected tables.
After the repair completed, some of the rows on the slave had been
deleted - so the Master a
an "rsync" with the right options from the unaffected slave to the corrupt
one might prove to be an elegant technique
Kishore Jalleda
On 3/7/06, Michael Jeung <[EMAIL PROTECTED]> wrote:
>
> Hi Folks,
>
> We've got a Single Master/Multiple Slave environment.
>
Hi Folks,
We've got a Single Master/Multiple Slave environment.
Recently, we had some corruption on one of the slaves and I had to
repair the affected tables.
After the repair completed, some of the rows on the slave had been
deleted - so the Master and the Slave weren't exactl
Given two MySQL database on two separate boxes in the same rack, one is
a master and the other is a slave.
Is corruption on either db possible in the case of a power outage that
affects both boxes? What is the best way to avoid this? Is it possible
to "roll back" the last N transac
.database.myodbc
Sent: Wednesday, January 11, 2006 2:13 PM
Subject: Mysql Server crashes saying Page directory corruption
Hi all,
Server version :4.0.26
OS: FeeBSD-4.10
The mysql server(slave) crashes with the following messages in its error
log, and gets restarted, after which rollbacks and st
Hi all,
Server version :4.0.26
OS: FeeBSD-4.10
The mysql server(slave) crashes with the following messages in its error
log, and gets restarted, after which rollbacks and starts replicating from
master
Page directory corruption: supremum not pointed to
051226 10:02:58 InnoDB: Page
10, 2006 9:00 PM
Subject: checking for corruption?
After a power outage, we had a large table (~2GiB, 23e6 records) get
corrupted. Only a few rows were actually affected, so nobody noticed for
a few weeks though. A repair fixed the problem.
We are now considering running the "check tab
After a power outage, we had a large table (~2GiB, 23e6 records) get
corrupted. Only a few rows were actually affected, so nobody noticed for
a few weeks though. A repair fixed the problem.
We are now considering running the "check table" command regularly
(every 15 minutes?) and plugging that int
Hi!
On Aug 09, Daniel Kasak wrote:
> Hi all.
>
> I've been testing out mysql-5.0.10 on my Powerbook ( Gentoo Linux PPC ),
> and I've hit an incredibly unfortunate bug. It is demonstrated
> adequately with the following:
...
> Is anyone interested in examining what went wrong? ie should I create
On Wednesday 10 August 2005 10:23 am, Daniel Kasak wrote:
> Fajar Priyanto wrote:
> >Well, it's not 5.0.x, it's 4.0.25-standard. I'm not sure how the error
> > appears in the first place. What I notice when I open the database using
> > phpMyadmin is that that particular troubled table status is "i
Fajar Priyanto wrote:
Well, it's not 5.0.x, it's 4.0.25-standard. I'm not sure how the error appears
in the first place. What I notice when I open the database using phpMyadmin
is that that particular troubled table status is "in use".
I'm allowed to ssh into the server, and hopefully I can s
On Wednesday 10 August 2005 06:50 am, Daniel Kasak wrote:
> A hosting provider running 5.0.x? That's whacky.
> When you say "my access to the shell is very limited", what does that
> mean exactly? Can you ssh in and run the 'mysql' command-line client? If
> you can, then do it, and you should be ab
Fajar Priyanto wrote:
This is what I think hit me too, Daniel.
Unfortunately, it's not on my own server (a hosting provider), so my access to
the shell is very limited.
My website is still running, but, I can't export the database using phpMyadmin
anymore, because the troubled table is on th
Timothy Smith wrote:
Hi, Daniel,
First, here's a trick that *should* work for dumping out the data.
Change directory to the MySQL data directory, and then use this little
shell command:
for d in mysql test; do (cd $d; tables=`/bin/ls -1 *.frm | sed -e s,\\.frm,,`;
mysqldump $d $tables); done
This is what I think hit me too, Daniel.
Unfortunately, it's not on my own server (a hosting provider), so my access to
the shell is very limited.
My website is still running, but, I can't export the database using phpMyadmin
anymore, because the troubled table is on the first list of tables.
D
Hi all.
I've been testing out mysql-5.0.10 on my Powerbook ( Gentoo Linux PPC ),
and I've hit an incredibly unfortunate bug. It is demonstrated
adequately with the following:
mysql> use entropy;
Database changed
mysql> show tables;
ERROR 1052 (23000): Column 'TABL
rsion. We had the same problems running on the
> > old RH 7.3 kernel (2.4.17 was it?) After upgrading to RH9 it was fine.
> >
> > Chris McKeever wrote:
> > > MySQL 4.0.16
> > >
> > > I am having this annoying persistent corruption issue, and am
> &g
e had the same problems running on the
> old RH 7.3 kernel (2.4.17 was it?) After upgrading to RH9 it was fine.
>
> Chris McKeever wrote:
> > MySQL 4.0.16
> >
> > I am having this annoying persistent corruption issue, and am
> > wondering if anyone has any suggesti
Also check your kernel version. We had the same problems running on the
old RH 7.3 kernel (2.4.17 was it?) After upgrading to RH9 it was fine.
Chris McKeever wrote:
MySQL 4.0.16
I am having this annoying persistent corruption issue, and am
wondering if anyone has any suggestions. I have two
Hello.
> MySQL 4.0.16
You run an old MySQL. Upgrade to the latest release sometimes solves
such issues. Check if the problem remains with MySQL 4.1.13 (or 4.0.25).
Chris McKeever <[EMAIL PROTECTED]> wrote:
> MySQL 4.0.16
>
> I am having this annoying persisten
On 7/28/05, Dan Tappin <[EMAIL PROTECTED]> wrote:
> I was running into this all the time.
>
> I actually had myisamchk running on a regular basis (live) via cron
> which I think was actually causing the corruption.
>
> By chance are you running myisamchk on the live ta
I was running into this all the time.
I actually had myisamchk running on a regular basis (live) via cron
which I think was actually causing the corruption.
By chance are you running myisamchk on the live tables?? I ran the
REPAIR TABLE... on each table, shut down mysql THEN ran myisamchk
On 7/28/05, Dobromir Velev <[EMAIL PROTECTED]> wrote:
> Hi,
> Isn't there some information in the MySQL error log about what might have
> caused the corruption. Normally this would happen when disk or memory problem
> occurs.
>
thanks for the reply -
from the .
Hi,
Isn't there some information in the MySQL error log about what might have
caused the corruption. Normally this would happen when disk or memory problem
occurs.
On Thursday 28 July 2005 17:45, Chris McKeever wrote:
> MySQL 4.0.16
>
> I am having this annoying persistent co
MySQL 4.0.16
I am having this annoying persistent corruption issue, and am
wondering if anyone has any suggestions. I have two tables that
refuse to stay clean. After a myisamchk (below) they show corruption.
I run a myisamchk -r, they get fixed, and the next day, they are once
again corrupt
So I've been poking around my system and I found
/usr/lib/mysql/
/usr/share/mysql/
The mod dates on these are really old. Can I delete these safely?
I'm guessing the are from the Apple install.
These files seem to be in the /usr/local/mysql/ path also. Hmmm... I
looked at my old Mac OS
On Jul 23, 2005, at 12:49 PM, Ware Adams wrote:
Then I don't know what to say about the MyISAM error, though I'd
watch InnoDB pretty carefully as I think MyISAM is pretty robust on
OS X too. We did also see these when a disk is failing, but I
assume you've run disk utility. I guess it co
http://www.innodb.com/ibman.php
In short, InnoDB deals better than MyISAM with crashes of the mysqld
server or the OS, but I don't think it's necessarily any better (nor
maybe could it be) with dealing with an underlying disk corruption
issue that keeps occurring.
I am also wo
On Jul 23, 2005, at 10:14 AM, Ware Adams wrote:
Has your mysql crashed or have your restarted the machine without
first shutting down mysql manually? We only saw this error when
mysql was not shut down normally. You can look in your .err file
which should be in your data directory. Ever
On Jul 23, 2005, at 11:56 AM, Dan Tappin wrote:
I am all most ready to give up on MySQL at this point. I'm still
getting regular table corruption on multiple installs of OS X.
I went as far as reporting it as a bug:
http://bugs.mysql.com/bug.php?id=12066
They seem to want more info b
I am all most ready to give up on MySQL at this point. I'm still
getting regular table corruption on multiple installs of OS X.
I went as far as reporting it as a bug:
http://bugs.mysql.com/bug.php?id=12066
They seem to want more info but my requests for clarification have
gone unans
On Jul 6, 2005, at 10:26 AM, [EMAIL PROTECTED] wrote:
I'm not a Mac guru but what you describe sounds like file system
corruption. Can you do a diagnostic scan of your hard drives
looking for bad sectors? You can move your data to another portion
of the disk if you run an ALTER TAB
Dan Tappin <[EMAIL PROTECTED]> wrote on 07/06/2005 11:26:13 AM:
> I am running into repeatable table corruption with MySQL 4.x on Mac
> OS X 10.x.
>
> I previously had a MySQL install on 10.2 Client under 3.x and never
> had an issue or any major problems at all. I
along the way.
Could the dump and restore perhaps fix this? Can I still do it with
out down grading?
Dan T
On Jul 6, 2005, at 9:26 AM, Dan Tappin wrote:
I am running into repeatable table corruption with MySQL 4.x on Mac
OS X 10.x.
I previously had a MySQL install on 10.2 Client under 3.
I am running into repeatable table corruption with MySQL 4.x on Mac
OS X 10.x.
I previously had a MySQL install on 10.2 Client under 3.x and never
had an issue or any major problems at all. I upgraded to MySQL 4.x
and have subsequently installed MySQL 4.x (from the supplied pkg's)
Hello.
Looks like a bug for me. I've reported it at:
http://bugs.mysql.com/bug.php?id=11494
David Sparks <[EMAIL PROTECTED]> wrote:
> db1 corruption # cat > my.sql
> DROP TABLE IF EXISTS service_contacts;
> CREATE TABLE service_contacts (
> croeated
db1 corruption # cat > my.sql
DROP TABLE IF EXISTS service_contacts;
CREATE TABLE service_contacts (
croeated datetime NOT NULL default '-00-00 00:00:00'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
INSERT INTO service_contacts VALUES ('2006-06-14 10:27:40');
db1 corrupti
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTEC
1 - 100 of 345 matches
Mail list logo
