Hi!
I changed it to upcoming 3.23.38 so that it prints an error message
and calls exit(1).
Since you can run out of disk space inside InnoDB only when starting
the database after adding new data or log files to my.cnf, there is
not much need for interaction. If InnoDB would archive its log files,
user interaction would be nice.
Regards,
Heikki
>Description:
My disc was full when I tried to restart mysql. The error log filled up
with:
Innobase encountered a problem with file /var/lib/mysql/ib_logfile0.
Disk is full. Try to clean the disk to free space
before answering the following: How to continue?
(Y == freed some space: try again) (N == crash the database: will restart
it)?
Innobase encountered a problem with file /var/lib/mysql/ib_logfile0.
Disk is full. Try to clean the disk to free space
before answering the following: How to continue?
(Y == freed some space: try again) (N == crash the database: will restart
it)?
.... Not clever for a daemon process :) >How-To-Repeat: see above>Fix:
output error to STDERR and quit with exit 1>Submitter-Id: <submitter ID>
>Originator: Christian Hammers>Organization: Debian GNU/Linux
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
