From owner-freebsd-current@FreeBSD.ORG Wed Mar 29 15:56:05 2006 Return-Path: X-Original-To: current@freebsd.org 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 8A96016A423; Wed, 29 Mar 2006 15:56:05 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECAD143D70; Wed, 29 Mar 2006 15:55:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2TFtvIW000624; Wed, 29 Mar 2006 08:55:57 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <442AAE0D.2080608@samsco.org> Date: Wed, 29 Mar 2006 08:55:57 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Suleiman Souhlal References: <20060328155316.GA20036@peter.osted.lan> <20060328180553.GA8364@xor.obsecurity.org> <442A8D86.9010903@FreeBSD.org> In-Reply-To: <442A8D86.9010903@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: current@freebsd.org, Kris Kennaway Subject: Re: Fun with df X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Mar 2006 15:56:05 -0000 Suleiman Souhlal wrote: > Kris Kennaway wrote: > >> On Tue, Mar 28, 2006 at 05:53:16PM +0200, Peter Holm wrote: >> >>> I've seen this problem on both RELENG_6 from Mar 27 19:37 UTC and HEAD: >> >> >> >> Have you figured out how to cause it? I and others see it >> occasionally (also things like this at reboot: >> >> /c: unmount pending error: blocks -68512 files 0 >> >> which dates back at least to 5.3). But I haven't been able to figure >> out how to trigger it on demand. > > > IIRC it's pretty easy to trigger: delete a lot of files, and unmount > right after as rm is done. > umount -f in the middle of the rm might also work. > > -- Suleiman So does this mean that dirty metadata buffers didn't get flushed? If so, where did they go? Or does it mean that certain metadata fields never even got updated? Sigh, what a mess =-( Does this happen with softupdates turned off? Scott