Hi!
>>>>> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes:
Peter> Hello mysql,
Peter> Any ideas how this may happen:
Peter> Mysql version 3.23.37, auto recovery turned on.
mysql> check table layers_st50.g00stat_sitepaths;
Peter>
+-------------------------------+-------+----------+----------------------------+
Peter> | Table | Op | Msg_type | Msg_text
|
Peter>
+-------------------------------+-------+----------+----------------------------+
Peter> | g00stat_sitepaths | check | warning | Table is marked as crashed
|
Peter> | layers_st50.g00stat_sitepaths | check | status | OK
|
Peter>
+-------------------------------+-------+----------+----------------------------+
Peter> 2 rows in set (24.32 sec)
Peter> Also I would report the folowing problem with auto recovery:
Peter> If auto recovery fails because of out of disk space problem, the
Peter> behavior is not mysql default (to wait until there are some space) but
Peter> the table becomes dammaged and is not retried to be recovered even
Peter> disk space is freeed.
Because repair, recovery and optimize may use a LOT of disk space we did a
long time ago define that when any of the above options are run, MySQL
will when out of disk stop the operation at once, remove the big
temporary files and mark the table as crashed.
We thought this was better than let the recovery use up all disk space
this way crash the whole system.
I will add a note to the documentation about this!
Regards,
Monty
---------------------------------------------------------------------
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
