From owner-freebsd-questions@FreeBSD.ORG Thu Jun 19 18:31:56 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9B65106567B for ; Thu, 19 Jun 2008 18:31:56 +0000 (UTC) (envelope-from prvs=pschmehl_lists=04997c689@tx.rr.com) Received: from ip-relay-001.utdallas.edu (ip-relay-001.utdallas.edu [129.110.20.111]) by mx1.freebsd.org (Postfix) with ESMTP id 85C538FC1E for ; Thu, 19 Jun 2008 18:31:56 +0000 (UTC) (envelope-from prvs=pschmehl_lists=04997c689@tx.rr.com) X-Group: RELAYLIST X-IronPort-AV: E=Sophos;i="4.27,673,1204524000"; d="scan'208";a="2265178" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-001.utdallas.edu with ESMTP; 19 Jun 2008 13:31:55 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id C88CE23DE3 for ; Thu, 19 Jun 2008 13:31:55 -0500 (CDT) Date: Thu, 19 Jun 2008 13:31:55 -0500 From: Paul Schmehl To: freebsd-questions@freebsd.org Message-ID: <08316AEE182673D114F84C15@utd65257.utdallas.edu> In-Reply-To: <485A9F53.4090306@boosten.org> References: <20080619035949.GB8205@shepherd> <4859FC8F.5020308@ibctech.ca> <421A1EE3E8C305AD72BBA2BE@utd65257.utdallas.edu> <485A9F53.4090306@boosten.org> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: /var full X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2008 18:31:56 -0000 --On Thursday, June 19, 2008 20:02:59 +0200 Peter Boosten 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 > 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 # find /var/ -inum 27131920 /var/db/entropy/saved-entropy.6 # ls -lsa /var/db/entropy/saved-entropy.6 2 -r-------- 1 operator operator 2048 Jun 19 17:33 /var/db/entropy/saved-entropy.6 So it could have been something else entirely, and when those files tried to write to /var it was already full? Why is operator running dd? Is it trying to fix the problem? -- Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer.