But while I copied all the table files from A (testing machine) to machine
B (real server), no data was writing into A's tables. Are you saying
that I have to shut down the mysqld on machine A or activate WRITE lock to
A before copying over to machine B?
Qunfeng
At 02:52 PM 5/27/2005, Eric Bergen wrote:
If you are copying a file that mysql is writing to sections of the file
are going to be from different points in time so when that all gets put
backtogether in one file on the other end it's going to be corrupt.
Qunfeng wrote:
No, I didn't shut down mysqld or read lock. Would you please elaborate it
a little more on why? Thanks a lot!
Qunfeng
At 01:05 PM 5/27/2005, Eric Bergen wrote:
Did you shut down mysqld or read lock before copying the table?
Qunfeng wrote:
Hi,
I am running MySQL 4.1.8-Max-log on two Linux machine (machine A and
machine B). In the past, I do a simple scp to transfer all the
database table file from one machine (A) to the other (B). After the
transferring, the table on B works well.
However, I am encountering a problem with transferring a big table
(with 11 million record). The table in A works but seems to be
corrupted after transferrring to B. When querying on the table at B, I
got "Got error 127 from storage engine".
I tried myisamchk -r tablename but I still got the same msg. Any idea?
Thanks in advance!
Qunfeng
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
