From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 17:21:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCCA316A421; Mon, 18 Feb 2008 17:21:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id B462913C4D3; Mon, 18 Feb 2008 17:21:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2541D46B45; Mon, 18 Feb 2008 12:21:24 -0500 (EST) Date: Mon, 18 Feb 2008 17:21:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jim Bryant In-Reply-To: <20080218142004.O49202@fledge.watson.org> Message-ID: <20080218171841.O49202@fledge.watson.org> References: <47B90868.7000900@electron-tube.net> <47B91080.9010109@electron-tube.net> <20080218142004.O49202@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 17:21:25 -0000 On Mon, 18 Feb 2008, Robert Watson wrote: > Hopefully this bug will get resolved shortly, and then we can evaluate if an > errata notice is necessary. FYI, I have been unable, thus far, to reproduce it with 150,000 entries in the root of a test file system on an 8.x kernel. I'm not set up to test 6.x and 7.x currently, and have other obligations tht will prevent me from setting up 6.x and 7.x test images for a few days. If people who can reproduce this problem could send kernel stack traces (etc) as a follow-up to the PR, that would be most helpful. Right now it's sparse on actual debugging data. Robert N M Watson Computer Laboratory University of Cambridge