> > > > > I've just accidentally run myisampack (myisampack Ver 1.22) on a table > >which > > > I still need to update. Is there anyway I can unpack it? > > > >myisamchk --unpack <table>.MYI > > > >http://dev.mysql.com/doc/mysql/en/myisamchk_repair_options.html > > > > Alec > > > > Thanks Alec, > > I haven't actually run myisamchk -rq --sort-index --analyze yet, only > myisampack on the MYD tables. Does that mean I don't need to worry?
No - I think your data is now packed, so you need to unpack it. I haven't done it myself, but one of my customers did exactly what you did last Friday, and recovered by using the myisamchk feature. I wans't there, so check the exact syntax from the manual.
Alec
OK, managed to unpack all the tables, although ran into a problem with one table where the myisamchk failed with an error 28 (filesystem full). I ran myisamchk on the table again (setting the tmp directory to a bigger filesystem) , and this time although it finished, it displayed lots of warnings about duplicate keys...
I ran myisamchk with -d:
# myisamchk -d url_visit
MyISAM file: url_visit Record format: Fixed length Character set: latin1 (8) Data records: 6826673 Deleted blocks: 1275276 Recordlength: 20
table description: Key Start Len Index Type 1 2 4 unique unsigned long 2 7 4 unique unsigned long 11 4 unsigned long 15 4 unsigned long 6 1 binary
and it seems to have deleted some blocks. I think I've lost some data? Is there anything I can do apart from a restore to fix this?
Thanks,
JS.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
