From owner-freebsd-fs Mon Feb 25 17:56:35 2002 Delivered-To: freebsd-fs@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id CA8B137B404 for ; Mon, 25 Feb 2002 17:56:31 -0800 (PST) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.11.4/8.9.3) with ESMTP id g1Q1uLi28550; Mon, 25 Feb 2002 17:56:21 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200202260156.g1Q1uLi28550@beastie.mckusick.com> To: Kris Kennaway Subject: Re: UFS panic on -stable Cc: Matthew Dillon , Ian Dowse , Tony Finch , fs@FreeBSD.ORG, fanf@chiark.greenend.org.uk In-Reply-To: Your message of "Mon, 25 Feb 2002 17:47:05 PST." <20020225174705.A63111@xor.obsecurity.org> Date: Mon, 25 Feb 2002 17:56:21 -0800 From: Kirk McKusick Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for the quick reply Kris. Do you have any idea what you are doing on /dev to cause the panic? If so, can you go through the /dev operations that you do and see if you can come up with a script that triggers the panic? If you cannot easily get the set of operations, it would be pretty trivial to hack up the mfs code to trace all the operations done on it. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message