>
>
> > > Hi,
> > >
> > > I have recently had a system crash that required the
> > > installation of a new hard drive. I have access to the
> > > files on the old hard drive, on which is a database I
> > > need to recover.
> > >
> > > I am running MySql 3.23.37 and all the tables in the
> > > datab
> > Hi,
> >
> > I have recently had a system crash that required the
> > installation of a new hard drive. I have access to the
> > files on the old hard drive, on which is a database I
> > need to recover.
> >
> > I am running MySql 3.23.37 and all the tables in the
> > database to be recovered
"Andy Hall" <[EMAIL PROTECTED]> wrote on 07/04/2004 09:50:19:
> Hi,
>
> I have recently had a system crash that required the installation of
> a new hard drive. I have access to the files on the old hard drive,
> on which is a database I need to recover.
>
> I am running MySql 3.23.37 and a
> Hi,
>
> I have recently had a system crash that required the
> installation of a new hard drive. I have access to the
> files on the old hard drive, on which is a database I
> need to recover.
>
> I am running MySql 3.23.37 and all the tables in the
> database to be recovered are MyISAM.
>
> How
Hi,
I have recently had a system crash that required the installation of a new hard drive.
I have access to the files on the old hard drive, on which is a database I need to
recover.
I am running MySql 3.23.37 and all the tables in the database to be recovered are
MyISAM.
How can I recover t
Hi!
> "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes:
>> I will have to include a warning in the comments section of the MySQL
>> documentation to NOT CONVERT MySQL SYSTEM TABLES FROM myISAM TO INNODB TYPE!
I have now added a warning about this to the manual.
Regards,
Monty
Jeremy,
At 11:37 PM 11/2/01 -0800, you wrote:
>On Fri, Nov 02, 2001 at 11:17:37PM +0200, Heikki Tuuri wrote:
>>
>> I looked now what MySQL does when it calls lock_external at startup:
>> it initializes MySQL system tables like 'host' and 'user'. I assume
>> you have not converted MySQL system ta
On Fri, Nov 02, 2001 at 11:17:37PM +0200, Heikki Tuuri wrote:
>
> I looked now what MySQL does when it calls lock_external at startup:
> it initializes MySQL system tables like 'host' and 'user'. I assume
> you have not converted MySQL system tables to InnoDB format? That is
> not allowed. They
> Stephen,
>
> At 01:37 PM 11/2/01 -0800, you wrote:
>>> Stephen,
>>>
>>> At 12:38 PM 11/2/01 -0800, you wrote:
Heikki,
Removal of the log= option and even the log-bin statement did not
help. I used the latest (2.23.44) RPMs from one of the mysql.com
mirrors. I don't think it'
Stephen,
At 01:37 PM 11/2/01 -0800, you wrote:
>> Stephen,
>>
>> At 12:38 PM 11/2/01 -0800, you wrote:
>>>Heikki,
>>>
>>>Removal of the log= option and even the log-bin statement did not help.
>>>I used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I
>>>don't think it's a download
> Stephen,
>
> At 12:38 PM 11/2/01 -0800, you wrote:
>>Heikki,
>>
>>Removal of the log= option and even the log-bin statement did not help.
>>I used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I
>>don't think it's a download issue because the problem originally
>>occured with the
Stephen,
At 12:38 PM 11/2/01 -0800, you wrote:
>Heikki,
>
>Removal of the log= option and even the log-bin statement did not help. I
>used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I don't
>think it's a download issue because the problem originally occured with the
>2.23.43 dis
Heikki,
Removal of the log= option and even the log-bin statement did not help. I
used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I don't
think it's a download issue because the problem originally occured with the
2.23.43 distribution.
The crash occurs within seconds of startin
Stephen,
I resolved now with the mysql-max-3.23.44...tar.gz distribution. I still do
not understand what mysqld is trying to do here. What distribution do you
use, or did you compile yourself?
0x807b90f handle_segfault__Fi + 383
0x8253c7a pthread_sighandler + 106
0x80cf21a change_active_index__1
> Stephen,
>
> I resolved the stack dump based on the 3.23.43 symbols file. I do not
> understand what mysqld is trying to do here. Are you sure the stack
> dump is from 3.23.43?
>
> 0x807b90f init_signals__Fv + 71
> 0x8253c7a __tfx + 26
> 0x80cf21a index_prev__11ha_innobasePc + 74
> 0x8078693 mys
Stephen,
I resolved the stack dump based on the 3.23.43 symbols file. I do not
understand what mysqld is trying to do here. Are you sure the stack dump is
from 3.23.43?
0x807b90f init_signals__Fv + 71
0x8253c7a __tfx + 26
0x80cf21a index_prev__11ha_innobasePc + 74
0x8078693 mysql_lock_remove__FP
I converted my myISAM tables to Innodb format and everything went fine. When
I restarted MySQL-Max (2.23.43) I noticed that my query log file was not
being accessed anymore so I included "log=/var/lib/mysql/server1.log" to
/etc/my.cnf. Running MySQL-Max this time though caused a continuous
restart
Hi,
> The server where the db was located got hacked and I had to
> reinstall the whole thing. The old HD is preserved as was
> and the server got a new HD. I moved the old db to the new
> disk and when I try to access it, I get the following error:
>
> mysql> use thedb;
> Can't read dir of '
"Kay Aleksic" <[EMAIL PROTECTED]> wrote:
> I am dealing with my first MySQL server/db, and I ran into some trouble.
>
> The server where the db was located got hacked and I had to reinstall the
> whole thing. The old HD is preserved as was and the server got a new HD. I
> moved the old db to the n
errno 13 is 'permission denied'.
It looks like your permissions aren't set correctly.
-Jeff
- Original Message -
From: "Kay Aleksic" <[EMAIL PROTECTED]>
To: "MySQL List (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 3:10 PM
data . I am talking from a windows environment maybe its
different on Linux.
root=mysql
sub1=data
sub2=thedb<---database files for thedb go here
-Original Message-
From: Kay Aleksic [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 09, 2001 2:10 PM
To: MySQL List (E-mail)
Subject:
Hi list,
I am dealing with my first MySQL server/db, and I ran into some trouble.
The server where the db was located got hacked and I had to reinstall the
whole thing. The old HD is preserved as was and the server got a new HD. I
moved the old db to the new disk and when I try to access it, I g
22 matches
Mail list logo
