From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 16:39:54 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1B8816A41F for ; Tue, 6 Dec 2005 16:39:54 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id E9F6743D5E for ; Tue, 6 Dec 2005 16:39:53 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 6 Dec 2005 16:39:49 +0000 (GMT) Date: Tue, 6 Dec 2005 16:39:48 +0000 From: David Malone To: "K.C.Huang-MLC" Message-ID: <20051206163948.GA83751@walton.maths.tcd.ie> References: <000601c5fa56$3bcd2a00$61a313a3@jhlh> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c5fa56$3bcd2a00$61a313a3@jhlh> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@freebsd.org Subject: Re: rm: Directory not empty ..(had tried chflag ...) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 16:39:54 -0000 On Tue, Dec 06, 2005 at 07:14:26PM +0800, K.C.Huang-MLC wrote: > Dear All: > I running fsck -y to a device, and I delete some files in the same time . > I found there were some files could'nt be delete.. > > message: > rm: old_files: Directory not empty > > I had tried > chflags -R noschg old_files > rm -rf old_files Did you run fsck until the filesystem is clean? If not try running fsck from single user mode a few more times. Another possibility is that this can sometimes happen with softupdates with fsck running in the background. If you wait for fsck to finish running in the background, then the problem should go away (this has been fixed in more recent FreeBSD releases). David.