From owner-freebsd-geom@FreeBSD.ORG Wed Oct 12 20:34:04 2005 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B20F816A420 for ; Wed, 12 Oct 2005 20:34:04 +0000 (GMT) (envelope-from josh@oplink.net) Received: from mail.oplnk.net (smtp.oplink.net [216.90.3.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 661DF43D45 for ; Wed, 12 Oct 2005 20:34:04 +0000 (GMT) (envelope-from josh@oplink.net) Received: from localhost (localhost [127.0.0.1]) by mail.oplnk.net (Postfix) with ESMTP id 4B005760D33 for ; Wed, 12 Oct 2005 15:32:54 -0500 (CDT) Received: from mail.oplnk.net ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30338-05 for ; Wed, 12 Oct 2005 15:32:54 -0500 (CDT) Received: from devious.oplink.net (devious.oplink.net [216.90.3.155]) by mail.oplnk.net (Postfix) with SMTP id 1FD99760D15 for ; Wed, 12 Oct 2005 15:32:54 -0500 (CDT) Date: Wed, 12 Oct 2005 15:33:12 -0500 From: Joshua Bell To: freebsd-geom@freebsd.org Message-Id: <20051012153312.71befe49.josh@oplink.net> Organization: Optimal Link X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-and-Spam-Scanned: by oplink.net email shield Subject: GEOM causes kernel panic X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2005 20:34:04 -0000 When ever I try to transfer large filesets to the raid after getting it setup and mounted, the server panics and reboots. Once the server is back online, the raid is set in `stale` and the kernel panics if I try to start the raid up. It is weird, as I can easily manipulate small files and use the drives as normal untill I attempt to transfer files onto the drives. I am getting no error messages remotely when attempting to restart the raid. This is the same problem that I experienced on 5.4-release, and am still experiencing on 5.4-stable. -Josh