So basically all the changes from those 18hrs were stored in logs and not yet commited to the database? So maybe if I just commited the logs every so often I wouldn't have this problem?
> > It depends if you had any kind of query logging enabled (binary or text) > .. If you started safe_mysqld with -l (that's text logging of queries) .. > or configured my.cnf with bin-log (that's binary logging).. > > You should be able to pipe/patch the logs against the database and let it > run all the updates... > > I fixed all my errors by simply: > 1. show tables > 2. check table name1, name2, etc.. > 3. any problems listed above > 4. repair table name1 (repeat) > > > On Wed, 20 Aug 2003, Brian Chan wrote: > >> hi, >> >> the power outage in ontario caused my server to crash. after i booted >> up >> again it was as if the past 18 hrs never happened. all the changes to >> the >> database were gone. is there anyway to recover the missing data? it's >> probably too late now since new data has been put into the database >> since >> then... >> >> I now also have errors with my database. I run myisamchk >> /var/lib/mysql/*/*.MYI -e -o -r >> and I get many errors such as: >> Found block that points outside data file at 9464 >> or >> Found block with too small length at 980; Skipped >> >> Is there anyway I can resolve these errors? >> >> Thanks, >> Brian. >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: >> http://lists.mysql.com/[EMAIL PROTECTED] >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
