Ya, I did that.
I read elsewhere that this was recommended for 4.1.9+.
I did
stop slave;
change master to master_log_file='{Relay_Master_Log_File}',
master_log_pos={Exec_master_log_pos};
start slave
And it gave the same error.
That is when I checked the binlogs and saw that it was corrupted at
{E
stop slave;
change master to master_log_file='Relay_Master_Log_File' ,
master_log_pos=Exec_master_log_pos;
#Get the values for the above command from your show slave status output.
start slave;
The above process should fix your problem.
On 9/4/07, Russell E Glaue <[EMAIL PROTECTED]> wrote:
>
I had a disk full error on the master MySQL (4.1.22), which was replicating to a
slave (4.1.22).
My question is, how do I recover a slave replica when the master had a disk full
error, space was freed, but the 'disk full' issue left a corrupted master
binlog?
1) Do I have to reinitialize the slav
