From owner-freebsd-questions Fri Mar 31 7:50:44 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 680FB37B8F0 for ; Fri, 31 Mar 2000 07:50:42 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA38928; Fri, 31 Mar 2000 09:50:35 -0600 (CST) (envelope-from dan) Date: Fri, 31 Mar 2000 09:50:35 -0600 From: Dan Nelson To: Len Conrad Cc: freebsd-questions@FreeBSD.ORG Subject: Re: fsck: UNREF 9 megs Message-ID: <20000331095035.A38259@dan.emsphone.com> References: <4.3.2.20000331140641.02f4f680@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.9i In-Reply-To: <4.3.2.20000331140641.02f4f680@mail.Go2France.com>; from "Len Conrad" on Fri Mar 31 14:24:08 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 31), Len Conrad said: > Gotta 3.4R with a full /. Fsck found a 9 megabyte UNREF FILE, which would > really unfill my / of 40 megs. fsck -p says this sucker is CLEARED. Do I > have reboot to get the filespace back? Yow! Fsck should never be run on a mounted filesystem. The kernel will be really confused when the contents of the filesystem changes. Shutdown, reboot into single-user mode, and fsck them again, to make sure you haven't damaged anything. That 9MB UNREF file is probably a logfile, or a tempfile that had been deleted while a program still held it open. It would have disappeared on a reboot anyway (or if you could file the process holding it open, you could kill just that process without having to reboot).. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message