Date: Thu, 19 Jun 2008 20:44:38 +0200 From: Peter Boosten <peter@boosten.org> To: Paul Schmehl <pschmehl_lists@tx.rr.com> Cc: freebsd-questions@freebsd.org Subject: Re: /var full Message-ID: <485AA916.30100@boosten.org> In-Reply-To: <08316AEE182673D114F84C15@utd65257.utdallas.edu> References: <EA09BDBE04BB7B81413DB590@Macintosh.local> <20080619035949.GB8205@shepherd> <DB82314EA03D57CB11849EA5@Macintosh.local> <4859FC8F.5020308@ibctech.ca> <BBBB9169909ADCA813DB44EE@utd65257.utdallas.edu> <A42873E7-6DCB-4F55-AC79-C14353880E7D@goldmark.org> <421A1EE3E8C305AD72BBA2BE@utd65257.utdallas.edu> <485A9F53.4090306@boosten.org> <08316AEE182673D114F84C15@utd65257.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Schmehl wrote: > --On Thursday, June 19, 2008 20:02:59 +0200 Peter Boosten > <peter@boosten.org> wrote: > >> Paul Schmehl wrote: >>>> >>>>> I'm leaning toward some sort of bug in mysql version 5.0.51 which >>>>> creates a temporary file (in the wrong place) and then doesn't >>>>> release it until it exhausts the space on the drive. In any case, >>>>> I'm going to report it to the mysql folks as such and hope they can >>>>> figure out what the cause is. >>>> >> >> try to find the file with >> # fstat | grep var >> >> >> This will give a list with inodes for open files (the 6th column). >> >> # find /var -inum <inode> >> > > Interesting. > >> From the last section of entries in dmesg.today: > > pid 73721 (dd), uid 2 inumber 27131920 on /var: filesystem full > pid 730 (mysqld), uid 88 inumber 27132148 on /var: filesystem full > > # find /var/ -inum 27132148 > /var/db/mysql/buttercup3-bin.000031 > > # ls -lsa /var/db/mysql/buttercup3-bin.000031 > 15856 -rw-rw---- 1 mysql mysql 16208184 Jun 19 03:28 > /var/db/mysql/buttercup3-bin.000031 Do you replicate this mysql server to another? If not, comment the log-bin directive in my.cnf. That'll take care of these binary logfiles. Peter > > So it could have been something else entirely, and when those files > tried to write to /var it was already full? > My first thought: mysql is just reporting something wrong, but isn't actually causing it. I've seen a partition filling up once by a deleted, yet open apache log file. No df nor du reported a full disk, yet it was. Restarting apache did the trick. Peter -- http://www.boosten.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485AA916.30100>