On 10/28/2004 8:07 AM, gerald_clark <[EMAIL PROTECTED]>
wrote:
>
>
> Paul Fierro wrote:
>
>> One of my slaves stopped running due to a corrupted relay log. The error
>> file shows:
>>
>> Error writing file 'dbs2.log' (errno: 28)
>> Er
Paul Fierro wrote:
One of my slaves stopped running due to a corrupted relay log. The error
file shows:
Error writing file 'dbs2.log' (errno: 28)
Error in Log_event::read_log_event(): 'read error', data_len: 160,
event_type: 2
$ perror 28
Error code 28: No space left on d
One of my slaves stopped running due to a corrupted relay log. The error
file shows:
Error writing file 'dbs2.log' (errno: 28)
Error in Log_event::read_log_event(): 'read error', data_len: 160,
event_type: 2
Error reading relay log event: slave SQL thread aborted because of I/
[EMAIL PROTECTED]
> Sent: Thursday, April 08, 2004 10:43 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Corrupted relay log
>
> Here's what I did to fix it... Excert from MySql Manual...
>
> When you back up your slave's data, you should back up these two small
> files
ile = '',
Master_log_pos = ;
Mysql:> Slave Start;
Does anyone see a problem with this method?
Thanks,
Jeff
> -Original Message-
> From: Jeff McKeon
> Sent: Thursday, April 08, 2004 8:54 AM
> To: [EMAIL PROTECTED]
> Subject: Corrupted relay log
>
>
>
Is there any way to fix a corrupted relay log on a slave?
Jeff
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
