BLOCK_SYNC_ERROR truncates my data
Hello,
I got a HD crash in my server and I had to recover the mysql files with recovery software. When I tried to read the data, mysql said it was corrupted, and the attempts I've made to recover it have been unsucessful! I've tried with myisamchk --extended-check, recreating the table and using the new .frm and .myi. I followed the instructions in the manual, but I always end up in the deadend of 'Wrong bytesec: 154-126-101 at linkstart: 0' and when I try to repair it, either with REPAIR TABLE or with myisamchk, I get 'Wrong bytesec: 154-126-101 at 0; Skipped' followed by a bunch of 'Found block that points outside data file' resulting on an empty data file.
I tried to debug myisamchk and got down to mi_dynrec.c, where the call to '_mi_get_block_inf' returns a info->header[0]=154, which sends a BLOCK_SYNC_ERROR back and generates the 'Wrong bytesec' error.
The documentation for BLOCK_SYNC_ERROR says /* Right data at wrong place */
Could anybody give me any clues on how to get this data into the right place? Is there any application to read the data out of a data file only with the .MYD file? My problem is that the important data in these tables are type 'mediumtext' and I guess mysql compress them and that's why I can not read it from the raw MYD file. Is there any way to get the text from the MYD file?
Thank you very much.
Subject
Views
Written By
Posted
BLOCK_SYNC_ERROR truncates my data
3861
March 21, 2005 09:06AM
2463
April 26, 2005 06:10AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.