From owner-freebsd-questions@FreeBSD.ORG  Mon Feb 11 13:46:18 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0F3A216A417
	for <freebsd-questions@freebsd.org>;
	Mon, 11 Feb 2008 13:46:18 +0000 (UTC)
	(envelope-from nospam@mgedv.net)
Received: from mail.mgedv.net (mail.mgedv.net [213.229.1.44])
	by mx1.freebsd.org (Postfix) with ESMTP id BF5BA13C465
	for <freebsd-questions@freebsd.org>;
	Mon, 11 Feb 2008 13:46:17 +0000 (UTC)
	(envelope-from nospam@mgedv.net)
Received: from www.mgedv.at (unknown [1.1.8.1])
	by mail.my.loop (mgedv) with ESMTP id 6388A1C7AFA
	for <freebsd-questions@freebsd.org>;
	Mon, 11 Feb 2008 14:46:16 +0100 (CET)
Message-ID: <7bb1a6effe580a0642ad575af01f0aaf95816333@standard.lan>
Date: Mon, 11 Feb 2008 14:46:16 +0100 (CET)
From: "no@spam@mgEDV.net" <nospam@mgedv.net>
To: freebsd-questions@freebsd.org
User-Agent: unixMail/1.0
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: re: strange panic: freebsd 6.3: ffs_alloccg: map corrupted [SOLVED]
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2008 13:46:18 -0000


> during copying ~350GB from one volume to another on
> the local machine (separate disks, separate fs's) i
> get the following panic:

> start = 0, len = 23691, fs = /newdata
> panic: ffs_alloccg: map corrupted
> KDB: enter: panic
> [ thread pid 835 tid 10070 ]
> stopped at kdb_enter +0x2c:  leave

for those, who are interested in:

this issue was not related to UFS but to GELI.
we were trying to use a 8KB sector size on the geli
provider, which caused the panic.
using 4KB as sector size works.

the command before:
geli init -bP -e 3DES -K /my/test.key -s 8192 /dev/da0

and after:
geli init -bP -e 3DES -K /my/test.key -s 4096 /dev/da0

cheers...