Am 28.01.2013 14:40, schrieb Andrew Moore:
> Dump and reload or use some scripting to create and drop some fake data to
> increase the lsn towards the 'future' value.
>
>
> http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql-innodb-log-in-the-future
>
For now i tend to solution 3, rsync
do you know is it possible only certain files ?
re,
wh
>
> On Mon, Jan 28, 2013 at 12:01 PM, walter harms <wharms@stripped> wrote:
>
>> hi list,
>>
>> i am using mysql 5.1.53.
>> after a crash i have the follwing error in my log:
>>
>> 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158
>> InnoDB: is in the future! Current system log sequence number 0 2494349480.
>> InnoDB: Your database may be corrupt or you may have copied the InnoDB
>> InnoDB: tablespace but not the InnoDB log files. See
>> InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
>> InnoDB: for more information.
>>
>> according to the doc's at
>> http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
>> I need to restore the database from scratch (short version). What i do not
>> understand is what
>> exactly is broken ? Whole DBM ? One Instance ? (mysqlcheck says all
>> tables are ok).
>>
>> Not all tables are INNODB. Is is possible to restore only immodb tables ?
>> (Having fun with forgein keys)
>>
>> Or is there a better way to handle this ?
>>
>> re,
>> wh
>>
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe: http://lists.mysql.com/mysql
>>
>>
>
