Hello.
Replication process runs tree threads, two on slave and one on master, so if your master was running with no free space it's behavior unpredictable and replication could halt. SHOW SLAVE STATUS usually reports errors. I would stop replication and setup it again using, for example, LOAD DATA FROM MASTER. But if the data size is huge enough I would check the master.info and relay-log.info and continue the replication from where it had stopped. See: http://dev.mysql.com/doc/mysql/en/slave-logs.html [EMAIL PROTECTED] wrote: > > I took a couple of days vacation last week and naturally the /data partition > of my database server filled up because of something I was running and had > forgotten about. So my backup guy, thinking to help out, gzipped all my .bin > logs. Now I am noticing replication seems to have stopped on my other > server. Not sure if the two events are related or not. It could be that > things got all hosed up not because of the gzipping but because the partition > filled up in the first place? Anyway, what do I do now? Do I need to do a > new dump and start replication all over again? > > --ja > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
