nt: Monday, February 04, 2013 4:35 AM
To: Larry Martell
Cc: wha...@bfs.de; mysql
Subject: Re: log sequence number InnoDB: is in the future!?
2013/2/3 Larry Martell
>
>
> We also ended up dropping the database and restoring from dumps.
> However all recent dumps ended up having a similar co
2013/2/3 Larry Martell
>
>
> We also ended up dropping the database and restoring from dumps.
> However all recent dumps ended up having a similar corruption and we
> were still getting the same errors. We had to go back to an October
> dump before it would come up cleanly. And our db is fairly la
Am 03.02.2013 15:30, schrieb Larry Martell:
> We also ended up dropping the database and restoring from dumps.
> However all recent dumps ended up having a similar corruption and we
> were still getting the same errors. We had to go back to an October
> dump before it would come up cleanly. And o
On Sun, Feb 3, 2013 at 7:23 AM, walter harms wrote:
>
>
> Am 02.02.2013 01:34, schrieb Larry Martell:
>> On Mon, Jan 28, 2013 at 5:01 AM, walter harms 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
Am 02.02.2013 01:34, schrieb Larry Martell:
> On Mon, Jan 28, 2013 at 5:01 AM, walter harms 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
On Mon, Jan 28, 2013 at 5:01 AM, walter harms 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
Am 28.01.2013 16:18, schrieb Andrew Moore:
> So this isn't production - well just rebuild it from a backup? It's a pain
> in the rear to get the lsn aligned again through data creation/removal but
> if it's a system critical instance without possible downtime you've got
> some work to do...
>
t
Am 28.01.2013 16:01, schrieb walter harms:
>
>
> 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
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 soluti
So this isn't production - well just rebuild it from a backup? It's a pain
in the rear to get the lsn aligned again through data creation/removal but
if it's a system critical instance without possible downtime you've got
some work to do...
On Mon, Jan 28, 2013 at 2:21 PM, walter harms wrote:
>
Am 28.01.2013 15:01, schrieb Manuel Arostegui:
> 2013/1/28 walter harms
>
>> 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 l
2013/1/28 walter harms
> 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
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
On Mon, Jan 28, 2013 at 12:01 PM, walter harms wrote:
> hi list,
>
> i am usi
13 matches
Mail list logo
