We've been using mysql version 4.7 on a FreeBSD 4.10 machine for the past few months, and while we've been putting a lot of load onto the DB, it's been stable. This past weekend, our sysadmin updated FreeBSD from 4.10 to 4.11, at which point mysql began having serious problems. The DB itself is fine, but the process in FreeBSD instead of spending CPU time ends up hung in a state of "biord", during which NO database operations can take place. From what I've been able to tell, this is a blocking I/O state, but what we can't figure out is why it's suddenly doing this, and how to get it to stop.
Other than standard start-stop-reboot and so on, here are several remedies we've tried: rollback to BSD 4.10. Blocking state remains. Upgrade mysql to latest release (also 4.11): Blocking state goes from 90% of the time to 50% or so, but remains. The next step we're going to try is to switch out hardware to a BSD 5 machine and hope that solves the issue. But we've had no luck trying to figure out what's happening. Other states we see are "ffsfsn" and the occasional "sbwait". Has anyone else had a similar issue, and if so how did you address it? Thanks! -- Joe -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
