Details
Minor
Description
I imported a few hundred gb of data and ran out of disk space, so I cancelled the import (Ctrl+C). At this point the logs show:
140919 15:12:54 [Warning] mysqld: Disk is full writing './mysql-bin.000055' (Errcode: 28 "No space left on device"). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 140919 15:12:54 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs 140919 15:14:54 [Warning] mysqld: Disk is full writing './mysql-bin.000055' (Errcode: 28 "No space left on device"). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 140919 15:14:54 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs 140919 15:24:54 [Warning] mysqld: Retry in 60 secs. Message reprinted in 600 secs
I forgot about it until today (2 days later) and attempted to stop the service (service mysql stop), but realised the disk space issue is probably blocking it. I freed 7gb (actually free, not open files locking space!) and tried to stop it again, with no success.
There appears to be no writes to the log or binlog.
"strace" shows:
futex(0x13a8904, FUTEX_WAIT_PRIVATE, 5, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x13a8904, FUTEX_WAIT_PRIVATE, 6, NULL
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Please comment to re-open if you have additional information.
Hi Marc,
Sorry for the delayed response.
What kind of import it was – loading a dump file via MySQL client, or executing LOAD DATA statement, or...?
Which engine(s) are you using?
Was the log (error log where the warnings were printed) in the same disk partition as the binlogs, so that it was also affected by the disk space problem?
Thanks