[SOLVED] "Verifying integrity of message store databases" taking too long

[goo0h]

At 7AM started an upgrade from 6.0.3 to 6.0.7 (after which I was going to drop in the small patch for 6.0.7.) The server is pretty loaded with about 14K accounts, but it's a quad, quad-core box. Maybe there's some mysql db tweaking I need to do to improve performance. Anyway, got this message shortly after 7AM, and it's been sitting there since (it's now 11:56AM):

Do you want to verify message store database integrity? [Y]
Verifying integrity of message store databases. This may take a while.
mysqld is alive

My question is this: is it safe to hit CTRL-C? When I run top, I see that mysqldb is taking about 100% of the cpu, so I'm guessing it's still working, but obviously don't know what's really going on. I'm not really noticing an error messages in the logs.

This is the first time attempted the upgrade with this many accounts on the system, but in the past it really didn't take that long, and seems to be taking disproportionately long this time.

Advice?????

[goo0h]

Yup, OK to hit ^C and do the upgrade without the integrity check.

[mmorse]

FYI you can run this check before ./install.sh if you want, as root:
cd /opt/zimbra/libexec
./zmdbintergrityreport -v