Quoting sheeri kritzer ([EMAIL PROTECTED]):
> According to the manual, 64 to 32 bit shouldn't matter, it should work
> fine as long as they're both little endian, or they're both big
> endian.
This friend of mine said he also had major problems moving 32->64.
Crashing mysql's, but not corrupt tables.
Well, i had crashing mysql's earlier (see my other post on this list
about MySQL on AMD64) but that seems over now. Now i have corrupt
tables. Or, better stated, all tables with indexes on them are corrupt.
> I've copied MyISAM tables from 64 to 32 bit without a problem.
Great to hear. Have to try it out myself to be sure though, but it's
good to hear you have no problems doing that.
> BTW, I suggested that because in the error it said:
> "myisamchk: error: Key in wrong position at page 715776
> - check records and index references"
> Did you by any chance symlink or move files, or not move the key
> files? My guess is that might cause that problem, otherwise, I have
> no idea what would cause it.
Nope. What i did is, in psuedocode:
for database in datadir/*
for table in datadir/database/*
lock table
flush table
binary copy table* to tempdir
unlock table
}
}
What seems like a normal binary copy to me.
All three files were copied, the .frm, the .MYI and the .MYD.
Regards,
Sander.
--
| 't Gaat om 't spel, niet om de knikkers!
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
