From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:16:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A48F16A4E5; Fri, 7 Jul 2006 14:16:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E38443D53; Fri, 7 Jul 2006 14:16:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2603646D54; Fri, 7 Jul 2006 10:15:58 -0400 (EDT) Date: Fri, 7 Jul 2006 15:15:58 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Bradley W. Dutton" In-Reply-To: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> Message-ID: <20060707151333.C51390@fledge.watson.org> References: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: graid3 rebuild panic: mb_dtor_pack: ext_size != MCLBYTES X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:16:00 -0000 On Thu, 6 Jul 2006, Bradley W. Dutton wrote: > I get the below panic when rebuilding a graid3 array. Is this indicative of > a hardware or software problem? Or is some of the data on my array corrupt > and I should just rebuild the array? I searched on google and didn't find > much. > > panic: mb_dtor_pack: ext_size != MCLBYTES As I can't ever remember seeing that panic before, which is compatible with google's conclusion, it's likely this is a sign of kernel memory corruption. Whether that is a result of a hardware problem, I can't say. Is this reproduceable? If so, it could be a graid3 memory corruption problem. I've CC'd Pawel, the author of graid3. Robert N M Watson Computer Laboratory University of Cambridge