MySQL损坏数据的恢复

核心提示： -e, --extend-checkTry to recover every possible row from the data fileNormally this will also find a lot of garbage rows;Don't use this optio

-e, --extend-check　Try to recover every possible row from the data file

Normally this will also find a lot of garbage rows;

Don't use this option if you are not totally desperate.

-f, --force　　　　 Overwrite old temporary files.

-k, --keys-used=#　 Tell MyISAM to update only some specific keys. # is a

bit mask of which keys to use. This can be used to

get faster inserts!

-r, --recover　　　 Can fix almost anything except unique keys that aren't

unique.

-n, --sort-recover　Forces recovering with sorting even if the temporary

file would be very big.

-p, --parallel-recover

Uses the same technique as '-r' and '-n', but creates

all the keys in parallel, in different threads.

THIS IS ALPHA CODE. USE AT YOUR OWN RISK!

-o, --safe-recover　Uses old recovery method; Slower than '-r' but can

handle a couple of cases where '-r' reports that it

can't fix the data file.

--character-sets-dir=...

Directory where character sets are

--set-character-set=name

Change the character set used by the index

-q, --quick　　　　 Faster repair by not modifying the data file.

One can give a second '-q' to force myisamchk to

modify the original datafile in case of duplicate keys

-u, --unpack　　　　Unpack file packed with myisampack.