Dear all,

one 5.0.13 ZCS system encounters a power failure reboot, after that, the ZCS will always do "db crash recovery" when services start up, something like this in mailbox.log:

Code:
2010-07-14 16:11:26,237 INFO  [main] [] RedoPlayer - Deferring crash recovery to after startup: txn 1274070006.40888 [IndexItem] ver=1.23, tstamp=1274072796408, mailbox=35278, id=4257385, type=5

2010-07-14 16:11:26,237 INFO  [main] [] RedoPlayer - Deferring crash recovery to after startup: txn 1274070006.40889 [IndexItem] ver=1.23, tstamp=1274072796408, mailbox=35278, id=4257397, type=5

2010-07-14 16:11:26,237 INFO  [main] [] RedoPlayer - Deferring crash recovery to after startup: txn 1274070006.40890 [IndexItem] ver=1.23, tstamp=1274072796408, mailbox=35278, id=4257378, type=5
How can i do a complete DB recovery so that it will not start it again when every reboot??

and the more serious problem is that the system now is suffering poor performance, the obvious messages in mailbox.log are something like:

Code:
2010-07-14 17:02:56,909 WARN  [Pop3Server-39] [name=xxxx@yyy.zzz;ip=209.85.216.6;] dbconn - Connection pool is 75% utilized (100 connections out of a maximum of 100 in use).  Turn on debug logging for zimbra.dbconn to see stack traces of connections not returned to the pool.

From the OS "top" utility, it looks to me the ZCS is performaing some heavy disk I/O activities, which caused iowait% pretty high.

any advice on this?

Thanks.