From owner-freebsd-questions@FreeBSD.ORG Sat Feb 2 10:45:08 2008 Return-Path: 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 6CD3216A420 for ; Sat, 2 Feb 2008 10:45:08 +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 2981A13C442 for ; Sat, 2 Feb 2008 10:45:08 +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 DB2491C751A; Sat, 2 Feb 2008 11:17:13 +0100 (CET) Message-ID: <585224f5dfe3f9c3cebf21ea56bb9f8bc46ceede@standard.lan> Date: Sat, 2 Feb 2008 11:17:13 +0100 (CET) From: "no@spam@mgEDV.net" To: "no@spam@mgEDV.net" 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 Cc: freebsd-questions@freebsd.org Subject: Re: strange panic: freebsd 6.3: ffs_alloccg: map corrupted X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2008 10:45:08 -0000 On Fri, February 1, 2008 16:30, no@spam@mgEDV.net wrote: > > hi folks, > > 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 > > the destination filesystem i created from scratch > today, and the other which is read from is fsck'd. > > because of privacy/security considerations, i cannot > really post the whole configuration of the machine > (like fs-layout, other details, dmesg will be ok if > needed). > > the backtrace can be viewed on this image: > http://www.mgedv.at/panic_ffs_alloccg.png > update: the filesystem is created using the following newfs-cmd: newfs -L newdata -O 2 -U -b 65536 -f 8192 -c 262144 -i 524288 -m 0 -o space /dev/amrd2 btw, i forgot to mention, that the panic is raised at different amounts of data being copied. so this does not seem like a hardware defect for me... anyone out there who has an idea? cheers...