Date: Thu, 1 Apr 2004 19:38:26 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Daryl Chance <chancedj@yahoo.com> Cc: current@freebsd.org Subject: Re: FBSD 5.2.1-p4 and mysqld problems Message-ID: <20040401193656.S35367@carver.gumbysoft.com> In-Reply-To: <20040401031036.77156.qmail@web9602.mail.yahoo.com> References: <20040401031036.77156.qmail@web9602.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> one of the problems we are having is that there is 1 > specific table in the db (and it's only 1 database too > that this happens) is getting corrupted and forcing us > to have to repair it. This one could just be a > problem with mysql and it's just accelerated w/ using > it on FreeBSD 5.x. We haven't nailed any specific > time that this happens nor any specific > insert/select/update that could cause it. Is there > any way to verify (through FreeBSD userland commands > or ports that you may know of) that this isn't a drive > problem? Is there something I can run on FBSD that > will help me to track this problem down (perhaps some > sort of GEOM logging)? How about moving the table file out of the way and recreating it? If theres some sort of uncorrected error showing up in the file, that should lock it away. > the other problem we are having is that mysql will > lock up. 1 of the mysqld processes freezes (uses up > all the cpu) and it won't allow anymore queries > against it until we shutdown. Is there any way for me > to debug this and find out where it is hanging? Is > there a working alternative to truss? Or should I > just compile option PROCFS in and use it next time it > locks? ps auxwwww | grep mysql and look at WCHAN. That will say what is blocked in. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040401193656.S35367>