Xavier,
I assume you have increased
innodb_buffer_pool_size
to 16M or bigger?
The fsync problem fixed in .40b could cause
that InnoDB was not able to flush modified
pages quickly enough to disk, causing the
error message 'Difficult to find free block..."
Please download the brand-new 3.23.41
from the MySQL site. (Though just a minute ago
the download links of MySQL -Max did not work yet.)
Try to restart then. Does the warning message
still appear?
Regards,
Heikki
http://www.innodb.com
Copied message:
.......................
Hi,
I guess somthing happenned this weekend and mysql
restarted.
After the doing a recovery scanning ..... messageI get the following:
Warning difficult to find free block try to increase memory buffer pool
size.
I have killed the process and increased the memory so now mysql is using
about 90.6 % of the memory but still the problem reappeared.
I unfortunatly do not have more memory to allocate,
and my mysql.err keeps growing and growing.
This is on Debian unstable/testing with 1gb of memory.
My questin is should I continue to wait, or plain and simply restart
everyting from scratch.Thanks for any tips.
Xavier
---------------------------------------------------------------------
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
