MySQL server_errno=1236 when disk full

Yesterday I was asked for help concerning a replication problem with one of our test systems. My colleague had already installed a fresh dump he had created with mysqldump ... --master-data. The dump looked ok and contained a master configuration statement:

...
CHANGE MASTER TO MASTER_LOG_FILE='master-bin.000127',MASTER_LOG_POS=4462223;
...

The slave was provided with the correct user, password and host name for this master. Nevertheless issuing a START SLAVE did not work. In the slave .err file we found this:

 
...
050327 20:54:51 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236)
050327 20:54:51 [ERROR] Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log
...

After some fiddling around and searching the net for solutions we had a look at the server as well. SHOW MASTER STATUS revealed seemingly correct values and SHOW MASTER LOGS also listed several binlog files, up to the one mentioned above (127).

Only by looking at the Windows console of the server we found out what was wrong. Upon logging in the operating system popped up a nice balloon message about "Low Disk Space On Drive E:". In fact low was slightly understated: The drive was full up to the last byte.

Interestingly MySQL happily moved the current position counter in the output of SHOW MASTER STATUS forward, even though the file could not be written. The manual chapter on How MySQL Handles a Full Disk claims that the server should wait until there is enough space available again, and I remember having seen some "Waiting for someone to free space" before. I will have to take a look into this again and file a support request if I cannot find an explanation.

Comments

Anonymous said…
Do you recall how you resolved this issue? I may be experiencing something similar. I'm getting:

070831 23:53:25 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)
070831 23:53:25 [ERROR] Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log

070831 23:53:25 [Note] Slave I/O thread exiting, read up to log 'db100-bin.000056', position 879532399
Sat Sep 01, 06:24:00 AM GMT+2
Daniel Schneller said…
Sorry, but as it was not a critical system we did not have the time to look further into it. What we did was just purge some of the older binlogs and reduced the time they are kept on the master. The slave was re-initialized.
Sat Sep 01, 12:27:00 PM GMT+2
Post a Comment

Popular posts from this blog

SAXParseException: -1:-1: Premature End Of File - Misleading error

Today I had to look at a piece of code a colleague had written, using my XPathAccessor class. She used it in a servlet which gets XML formatted requests. As those are generated by an external 3rd party tool we agreed on some XML schema definitions. Everything they send us needs to conform to its corresponding schema, each reply we send gets validated against a different set. In order to allow independent testing on either side, we provided a little test kit that allows testing our system without having to set up a servlet engine. Basically it just takes a file, reads it into a String and hands that to the handler. First it gets parsed without validation. This is necessary to find out which type of request we were send (the address is the same for all of them). After the root element is known, it will be read again, this time using the right schema to verify the request. Once that is done, some reply is put together and sent back to the client. So far, so good. When I looked at
Read more

Something to know about Toshiba external USB HDD

As I wrote before, luckily I bought an external hard disk and started backing up my data just in time. Well, although this may look like talking bad about good things, I still believe I should post this. The drive model I bought is a Toshiba PX1269E-G50, a 500GB external USB 2.0 model. On the box it says this: Optimized for digital video, photos and music storage. Fanless design for near-silent operation. Interface: high-speed USB 2.0. Interface transfer rate (max.): 480 Mbps. Rotational speed: 7200 rpm. Cache: 16 MB. PushButton Backup. Password security. System requirements: PC with minimum 233 MHz pentium or equivalent (Celeron, AMD, etc.), Windows 2000/XP, available USB 2.0 port. I read this before buying in the store. I did not care for whatever "PushButton Backup" is. I still don't. I did not care for Password security. I still don't. It says Windows 2000/XP, but after all it is a USB mass storage device. Not needing the nifty Windows backup or security tools
Read more

Amiga 500 Restoration: A501 Memory Expansion

Image
The previous posts were mostly about cosmetics. This one is more technical, dealing with the repair and some preventative maintenance of the A501 memory expansion card. If you are curious to learn more about the retrobrighting of the computer’s case, don’t worry — I’ll get back to that at a later time. This is the third post in a series about restoring an Amiga 500 back to its former glory. Here are all of them so far. I’ll try to remember to update this in all related entry. 2017-12-24:  Amiga 500 Restoration 2018-01-05: Retrobrighting I 2018-02-05: A501 Memory Expansion 2018-02-05: Mouse and Mainboard Maintenance Amiga Memory — The Basics When the Amiga 500 was first introduced, it came with 512KB of memory. That was already double the amount the original Amiga 1000 had, but still not a whole lot. Especially when developers started to get familiar with the audio and video capabilities of the machine, RAM became a limiting factor in what you could do. Merely copying a single
Read more