From owner-freebsd-questions@FreeBSD.ORG Fri Feb 25 03:20:34 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 BB2DF16A4CE for ; Fri, 25 Feb 2005 03:20:34 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 499DD43D1D for ; Fri, 25 Feb 2005 03:20:34 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j1P3KX7O098457; Thu, 24 Feb 2005 21:20:33 -0600 (CST) (envelope-from dan) Date: Thu, 24 Feb 2005 21:20:33 -0600 From: Dan Nelson To: "T.F. Cheng" Message-ID: <20050225032032.GE60363@dan.emsphone.com> References: <20050225011427.57070.qmail@web51002.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050225011427.57070.qmail@web51002.mail.yahoo.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: FreeBSD cc: Piter Subject: Re: Directory not empty 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: Fri, 25 Feb 2005 03:20:34 -0000 In the last episode (Feb 25), T.F. Cheng said: > yeah, it's weird. I found that I can rename it (to tmp) then I tried > to del it: > > rm -fr tmp > rm: tmp/qt-x11-free-3.3.4/doc: Directory not empty > rm: tmp/qt-x11-free-3.3.4/src: Directory not empty Do you use softupdates, and did your system happen to crash after a portupgrade? I bet if you cd into tmp/qt-x11-free-3.3.4/doc and run ls -la, you'll see something like: $ ls -la total 2 drwx------ 4 dan dan 512 Feb 22 11:00 ./ drwxr-xr-x 3 dan dan 512 Feb 22 11:00 ../ The "." entry should have 2 links in an empty directory (one here, and one in the parent directory). That's caused be a failed background fsck, which is supposed to reset bad link counts after a crash. If you check /var/log/messages, you might see something like this: PARTIALLY TRUNCATED INODE I=316179 UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Try rebooting and letting the bgfsck run again, or boot into single-user mode and run fsck -p on the filesystem. -- Dan Nelson dnelson@allantgroup.com