From owner-freebsd-current@FreeBSD.ORG Wed Mar 29 17:27:23 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 58D7E16A426 for ; Wed, 29 Mar 2006 17:27:23 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 9DA6043D6A for ; Wed, 29 Mar 2006 17:27:19 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 80250 invoked from network); 29 Mar 2006 17:27:17 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 29 Mar 2006 17:27:17 -0000 X-pair-Authenticated: 83.95.197.184 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.4/8.13.4) with ESMTP id k2THRHlR048912; Wed, 29 Mar 2006 19:27:17 +0200 (CEST) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.4/8.13.4/Submit) id k2THRCWc048907; Wed, 29 Mar 2006 19:27:12 +0200 (CEST) (envelope-from pho) Date: Wed, 29 Mar 2006 19:27:12 +0200 From: Peter Holm To: Suleiman Souhlal Message-ID: <20060329172712.GA48623@peter.osted.lan> References: <20060328155316.GA20036@peter.osted.lan> <20060328180553.GA8364@xor.obsecurity.org> <442A8D86.9010903@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <442A8D86.9010903@FreeBSD.org> User-Agent: Mutt/1.4.2.1i 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 17:27:23 -0000 On Wed, Mar 29, 2006 at 03:37:10PM +0200, 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. > Yes! I created a few hundred thousand empty files, umount + fsck + mount without any problems. The df corruption started the moment I began deleting the files. The following umount gave this warning: /tmp: unmount pending error: blocks 4137248 files 0 - Peter > -- Suleiman