From owner-freebsd-geom@FreeBSD.ORG  Thu Jun  1 13:52:37 2006
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
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 3CD1816A4A5
	for <freebsd-geom@freebsd.org>; Thu,  1 Jun 2006 13:52:37 +0000 (UTC)
	(envelope-from snow@teardrop.org)
Received: from silver.teardrop.org (silver.teardrop.org [66.92.75.234])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B6DC943D45
	for <freebsd-geom@freebsd.org>; Thu,  1 Jun 2006 13:52:36 +0000 (GMT)
	(envelope-from snow@teardrop.org)
Received: by silver.teardrop.org (Postfix, from userid 100)
	id A1DE7C12B; Thu,  1 Jun 2006 09:52:35 -0400 (EDT)
Date: Thu, 1 Jun 2006 09:52:35 -0400
From: James Snow <snow@teardrop.org>
To: freebsd-geom@freebsd.org
Message-ID: <20060601135235.GB80106@teardrop.org>
References: <20060601133750.GA80106@teardrop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060601133750.GA80106@teardrop.org>
User-Agent: Mutt/1.4.2.1i
Subject: Re: graid3: FAILURE - out of memory in start
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GEOM-specific discussions and implementations
	<freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jun 2006 13:52:37 -0000

On Thu, Jun 01, 2006 at 09:37:50AM -0400, James Snow wrote:
> 
> Is there any debugging information I can enable to help
> solve this?  

Digging through sysctl -a it would seem that kern.geom.raid3.debug is a
good place to start.  Anything else I should try?


-Snow