Date: Thu, 31 Aug 2000 23:01:18 +1200 From: "Dan Langille" <dan@langille.org> To: Don Read <dread@texas.net> Cc: questions@FreeBSD.ORG Subject: RE: /var fills up with SQL191e_0.ISD, SQL191e_0.ISM Message-ID: <200008311101.XAA81403@ducky.nz.freebsd.org> In-Reply-To: <XFMail.000830203436.dread@texas.net> References: <200008290940.VAA66582@ducky.nz.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Aug 2000, at 20:34, Don Read wrote: > These look like temporary mysql files, is your mysql server crashing on a > particular query ? Don, thanks for the reply. I think I've figured this out. I believe it was "normal" processing. After running some tests, I noticed /var jump to 50% easily. If more than a couple of those queries ran concurrently, I'm sure /var would fill to 100%. /var was only 20MB, so I gave it more space. It's been about 24hrs since that move, and all seems well so far. Does that explanation sound plausible? See http://freebsddiary.org/file-system-full.html for details. > check /var/db/mysql/*.err (default, your data-dir may be elsewhere). I had a look at that. But I don't see anything in there which indicated a problem which would cause the symptoms. Rather, I saw problems which were caused by /var being at 100% rather than something which would cause /var to fill. Things such as: 000725 8:12:31 /usr/local/libexec/mysqld: Forcing close of thread 21309 user: 'xyz' 000725 8:13:13 Aborted connection 21392 to db: 'abc' user: 'xyz' cheers -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ FreshPorts - http://freshports.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008311101.XAA81403>