From owner-freebsd-current@FreeBSD.ORG Wed Jun 30 01:44:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2474A16A53D for ; Wed, 30 Jun 2004 01:44:30 +0000 (GMT) Received: from update.ods.org (221056.ds.nac.net [66.246.72.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB84343D58 for ; Wed, 30 Jun 2004 01:44:27 +0000 (GMT) (envelope-from jd@ods.org) Received: from localhost (221056.ds.nac.net [127.0.0.1]) by update.ods.org (Postfix) with ESMTP id C0A34154FA2 for ; Tue, 29 Jun 2004 21:43:26 -0400 (EDT) Received: from update.ods.org ([127.0.0.1]) by localhost (update.ods.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61054-02 for ; Tue, 29 Jun 2004 21:43:26 -0400 (EDT) Received: from [10.0.2.3] (pcp08928390pcs.anapol01.md.comcast.net [68.50.232.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by update.ods.org (Postfix) with ESMTP id 2F1E0154FA0 for ; Tue, 29 Jun 2004 21:43:26 -0400 (EDT) Date: Tue, 29 Jun 2004 21:43:28 -0400 From: Jason DiCioccio To: freebsd-current@freebsd.org Message-ID: <91000D21DD9308732A83EF3F@[192.168.2.1]> X-Mailer: Mulberry/3.1.3 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at ods.org X-Mailman-Approved-At: Wed, 30 Jun 2004 11:37:48 +0000 Subject: Cannot delete directory after crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2004 01:44:32 -0000 Greetings, This is just to report a problem I had recently with FreeBSD 5-CURRENT (from a couple of weeks ago) with a full filesystem. The box first froze due to an FS being full for an extended period of time (I've seen it happen before with 4.x as well). After having the box rebooted, it came back up and I started clearing out some space on it. What I did not realize until later was that fsck -B was running on that filesystem. This caused rm to obviously have no effect since there was an active snapshot of the filesystem. Free space remained about the same. The main problem I encountered though was that there were some directories that i could not delete. rm -rf would constantly return an error saying that the directory was not empty. After running fsck -fy on it, the problem appears to have gone away. I have a theory on why I think this happened though... I think that the snapshot code was trying to write data to a filled disk (copy on write) while I was deleting a bunch of files and fsck was running. This is my theory on why softupdates was unable to do its job properly. I can't confirm that, but I think it might be something worth looking into. Is the snapshot code smart enough to deal with that situation? Let me know if this makes any sense. I am also off list, so please CC me in any replies. Thanks in advance! -JD-