Bug #16264 | MySQL hangs ugly if no space on device | ||
---|---|---|---|
Submitted: | 6 Jan 2006 19:38 | Modified: | 9 Jan 2006 10:26 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: General | Severity: | S4 (Feature request) |
Version: | 5.0.16-standard | OS: | Linux (Fedora Core 4 2.6.13 in VMWare) |
Assigned to: | CPU Architecture: | Any |
[6 Jan 2006 19:38]
Philip Stoev
[8 Jan 2006 11:12]
Valeriy Kravchuk
Thank you for a problem report. It looks like a feature request for me. Do you agree?
[8 Jan 2006 12:33]
Philip Stoev
Yes, I agree. Please note however that from a public-relations standpoint any issues relating to incomplete/incorrect error reporting and inability to restart the server should have their prioirity increased a bit.
[9 Jan 2006 10:26]
Valeriy Kravchuk
Let's ask for the following feature: mysqld_safe (and, maybe, other startup scripts) should be changed to handle problems like the following: /usr/sbin/mysqd: Error writing file '/var/lib/mysql/hostname.pid` (Errcode: 28) Can't start server: can't create PID file: No space left on device properly. There is no need to keep restarting with the same "rate" until the problem is solved. So, some status code checks and/or error log checks should be added to the script.