From owner-freebsd-questions Sat Jul 15 8:16:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from c004.sfo.cp.net (c004-h015.c004.sfo.cp.net [209.228.14.102]) by hub.freebsd.org (Postfix) with SMTP id C755A37B99C for ; Sat, 15 Jul 2000 08:16:45 -0700 (PDT) (envelope-from rick@geckobot.com) Received: (cpmta 26775 invoked from network); 15 Jul 2000 08:16:44 -0700 Received: from chnd1-blk1-hfc-0251-d1db0086.rdc1.az.coxatwork.com (HELO patches) (209.219.0.134) by smtp.geckobot.com with SMTP; 15 Jul 2000 08:16:44 -0700 X-Sent: 15 Jul 2000 15:16:44 GMT Message-ID: <000901bfee70$930772f0$0464a8c0@patches> From: "Rick Moore" To: Subject: File System > 100% full Date: Sat, 15 Jul 2000 08:23:05 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone! I have found a bug with mysql on FreeBSD in that it uses about 4x the disk space when repairing the database. I've submitted to the bug to the mysql folks with the following df -k results to show the unusually large disk space used: su-2.03# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0a 49583 27125 18492 59% / /dev/ad0f 16027176 11486575 3258427 78% /usr /dev/ad0e 19815 2209 16021 12% /var /dev/vinum/raid 69546157 65076511 -1094046 102% /usr/local/mysql/var/g procfs 4 4 0 100% /proc Unfortunately, the result I got back was: "Your file system is broken. It can't possibly be 102% used" (They do most of their work on Linux and Solaris.) I know this is normal for some UNIX's to behave this way, but I can't find any documentation on it. Could someone please confirm that this is the correct behavior for FreeBSD? If this is documented somewhere, I'd love to know where... ALSO I've noticed that mysql uses all the file system space, but there are no files created! I think this is a clue. I've seen this happen if one process is writing a large file and another process deletes it prior to completion. In this case, the file system space continues to drain away but no file is apparently using it. Does anyone know any other ways this can happen? Thanks in advance! Regards, Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message