From owner-freebsd-stable@FreeBSD.ORG  Fri Aug 24 01:29:18 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4EE7416A417
	for <stable@freebsd.org>; Fri, 24 Aug 2007 01:29:18 +0000 (UTC)
	(envelope-from freebsd@chillt.de)
Received: from dd15624.kasserver.com (dd15624.kasserver.com [85.13.136.215])
	by mx1.freebsd.org (Postfix) with ESMTP id 123FD13C457
	for <stable@freebsd.org>; Fri, 24 Aug 2007 01:29:17 +0000 (UTC)
	(envelope-from freebsd@chillt.de)
Received: from takahe.local (84-203-32-212.mysmart.ie [84.203.32.212])
	by dd15624.kasserver.com (Postfix) with ESMTP id 912B11830AD10
	for <stable@freebsd.org>; Fri, 24 Aug 2007 03:29:15 +0200 (CEST)
Message-ID: <46CE346A.1020301@chillt.de>
Date: Fri, 24 Aug 2007 02:29:14 +0100
From: Bartosz Fabianowski <freebsd@chillt.de>
User-Agent: Thunderbird 2.0.0.6 (X11/20070811)
MIME-Version: 1.0
To: stable@freebsd.org
References: <46CDA657.9080201@chillt.de>
In-Reply-To: <46CDA657.9080201@chillt.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Re: Panic and reboot with USB hard disk
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2007 01:29:18 -0000

With the help of some folks in #freebsd on freenode, I have since been 
able to fix this problem. Here is the solution for future reference:

There is a bug in GELI that makes it corrupt data and panic kernels when 
certain non-standard settings are used. I had set the GELI sector size 
to 8192 and the AES key length to 256. After reinitializing GELI with 
sector size 4096 and AES key length 128, the problems have vanished. 
Even under extreme I/O load to the drive, the kernel does not panic and 
no data corruptions occur.