From owner-freebsd-questions Wed May 24 19:21:58 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id B54F137BBBF for ; Wed, 24 May 2000 19:21:55 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Received: from wartch.sapros.com (localhost [127.0.0.1]) by wartch.sapros.com (8.9.3/8.9.3) with ESMTP id TAA42220; Wed, 24 May 2000 19:21:00 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200005250221.TAA42220@wartch.sapros.com> To: Lowell Gilbert Cc: freebsd-questions@freebsd.org Subject: Re: Disappearing disk space. Date: Wed, 24 May 2000 19:21:00 -0700 From: Peter Haight Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It may be files that are unlinked but still open. The space won't be >available until the fiiles are closed. fstat(1) may help you track >them down. You'll find everything settled out next time you reboot, >of course, because *all* tasks are forced to let go of their files >then. Yep, it turned out it was natd that was the culprit. The log file had gotten deleted while it was running. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message