From owner-freebsd-questions@FreeBSD.ORG Fri Oct 15 16:36:13 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3840F16A4DE for ; Fri, 15 Oct 2004 16:36:13 +0000 (GMT) Received: from mail.jbco.com (jbco.feynman.net [209.218.104.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8580C43D1D for ; Fri, 15 Oct 2004 16:36:12 +0000 (GMT) (envelope-from stevel@jbco.com) Received: from nt-server.jbco.com (nt-server.jbco.com [192.168.100.33]) by cleanmail.jbco.com (Postfix) with SMTP id 088663A1D5 for ; Fri, 15 Oct 2004 09:36:11 -0700 (PDT) Received: (from STEVEL [192.168.100.200]) by nt-server.jbco.com (SAVSMTP 3.1.0.29) with SMTP id M2004101509361127540 for ; Fri, 15 Oct 2004 09:36:11 -0700 From: "Steven Lawson" To: Date: Fri, 15 Oct 2004 09:36:10 -0700 Message-ID: <000201c4b2d5$1455ec10$c864a8c0@STEVEL> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: malloc: wrong bucket panic X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 16:36:13 -0000 Not sure how to isolate this. It has only happened once in the past few months that this server has been installed, but it's a critical server and the first time I've ever had a FreeBSD box have a kernel panic! I'm running 4.10-RELEASE, IDE root & usr, vinum raid5 with 3 SCSI drives, firewire ide for backup, samba for storing everyones "My Documents", NFS client for access to an old SCO box via a samba share. Weekly the ide and raid5 gets dumped to files on the firewire drive which is then swapped for the following week. Daily a number of files on the raid5 get tar'd and gzip'd to another directory on the raid5. The panic occured during one of these sessions. The system was locked up tight in "syncing disks", I'm assuming because vinum needs malloc to finish the sync. Although it occurred while vinum was very busy, is it likely it's vinum or could vinum have tripped over something done by something else (such as the firewire swapping)? Is there any way to get more information if it happens again (I couldn't log in or anything)? I googled the "wrong bucket" error and found many references to it, but nothing that really indicated the conditions that would cause it to occur.