From owner-freebsd-questions@FreeBSD.ORG Tue Jan 4 00:22:21 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB23216A4CE for ; Tue, 4 Jan 2005 00:22:21 +0000 (GMT) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.FreeBSD.org (Postfix) with SMTP id 3450B43D48 for ; Tue, 4 Jan 2005 00:22:21 +0000 (GMT) (envelope-from dkelly@HiWAAY.net) Received: (qmail 10081 invoked by uid 0); 4 Jan 2005 00:27:29 -0000 Received: from user-69-73-60-132.knology.net (HELO ?10.0.0.68?) (69.73.60.132) by smtp8.knology.net with SMTP; 4 Jan 2005 00:27:29 -0000 In-Reply-To: <41D9C7BC.2050309@bouncebk.com> References: <41D9C7BC.2050309@bouncebk.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Kelly Date: Mon, 3 Jan 2005 18:22:14 -0600 To: mccyron@kc.rr.com X-Mailer: Apple Mail (2.619) cc: freebsd-questions@freebsd.org Subject: Re: 4.8 - / out of space X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 00:22:21 -0000 On Jan 3, 2005, at 4:31 PM, McCy Ron wrote: > System: FreeBSD 4.8 with standard config on PII/400...used mainly as a > backup server. > > df shows... > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad0s1a 128990 119660 -988 101% / > /dev/ad0s1f 257998 4 237356 0% /tmp > /dev/ad0s1g 7426528 2109420 4722986 31% /usr > /dev/ad0s1e 257998 15888 221472 7% /var > procfs 4 4 0 100% /proc > > My root file system is full and I can't account for why this is so. I > used du on all of the directories on / and could only come up with > 28000K of usage - far short of what it's supposed to hold. The User > Manual suggests that there my be some files not accounted for by du > actually residing on the system. What is the best way to reclaim this > space? A common goof is for a root user to mistype a device name causing a file to be created in /dev/ containing the data which was written. Tar will happily create such a file. Another goof is for root to "write" to an unmounted filesystem. Later when the filesystem is mounted the written files are hidden yet still consume space on the fs containing the mount point (usually /). If the results from "du -xsk /" and "df -k /" are not real close then I suspect you have written files in a directory which was later used as a mount point. dkelly@Opus [1003] du -xsk / 59003 / dkelly@Opus [1004] df -k / Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 253678 59004 174380 25% / dkelly@Opus [1005] -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.