se to corrupt all the
binlogs
John Mancuso
Linux Administrator/MySQL DBA
IT Infrastructure
American Home Mortgage
w: 631-622-6382
c: 516-652-2475
-Original Message-
From: Michael Dykman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 27, 2007 11:33 AM
To: John Mancuso
Subject: Re: B
Mancuso
Linux Administrator/MySQL DBA
IT Infrastructure
American Home Mortgage
w: 631-622-6382
c: 516-652-2475
-Original Message-
From: Michael Dykman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 27, 2007 12:04 PM
To: John Mancuso
Cc: mysql@lists.mysql.com
Subject: Re: Binlog errors
Do
t's no excuse to corrupt all the binlogs
John Mancuso
Linux Administrator/MySQL DBA
IT Infrastructure
American Home Mortgage
w: 631-622-6382
c: 516-652-2475
-Original Message-
From: Michael Dykman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 27, 2007 11:33 AM
To: John Mancuso
Subje
cture
American Home Mortgage
w: 631-622-6382
c: 516-652-2475
-Original Message-
From: Michael Dykman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 27, 2007 11:33 AM
To: John Mancuso
Subject: Re: Binlog errors
Not that any ideas are jumping out at me but what file system are you
employing
This seems to be a frequent occurrence:
[EMAIL PROTECTED] dblog]# mysqlbinlog mysql.25
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
ERROR: Error in Log_event::read_log_event(): 'Found invalid event in
binary log', data_len: 94, event_type: 15
Could not read entry at offset 4:Error
