From owner-freebsd-current@FreeBSD.ORG Tue Jun 26 13:52:16 2007 Return-Path: X-Original-To: Current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4660E16A400 for ; Tue, 26 Jun 2007 13:52:16 +0000 (UTC) (envelope-from freebsd-current@jschmidle.org) Received: from mxintern.schlund.de (mxintern.schlund.de [212.227.126.205]) by mx1.freebsd.org (Postfix) with ESMTP id 0AAF013C45B for ; Tue, 26 Jun 2007 13:52:16 +0000 (UTC) (envelope-from freebsd-current@jschmidle.org) Received: from [172.17.24.193] (helo=[172.17.24.193]) by mxintern.kundenserver.de with esmtp (Exim 4.50) id 1I3BHj-0005ub-Qr for Current@FreeBSD.org; Tue, 26 Jun 2007 15:40:47 +0200 Message-ID: <46811756.105@jschmidle.org> Date: Tue, 26 Jun 2007 15:40:38 +0200 From: Jan Schmidle User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-UI-Msg-Verification: b1083c5d5de4bde8e028c06541809d4c Cc: Subject: ZFS deadlocks or panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 13:52:16 -0000 I'm trying to bild a storagebox with ZFS. Now I have some problems which seems to be related to ZFS. Perhaps after adding disks to an existing pool, all consoles trying to execute a command with I/O operations freezes. Only sometimes I get a panic. I played around with the tuning variables, proposed in http://wiki.freebsd.org/ZFSTuningGuide but didn't help. The box is running -CURRENT amd64/SMP in a GENERIC configuration. Last cvsup and build was "Fri Jun 22" I also tried with i386 with and without SMP. I collected some Information and uploaded it to https://jschmidle.org/upload/ In "panic1" you can see a whole system-bootup resulting in a Panic. "panic2" is just another lockup during bootup. "areca" contains the information about the raid controller in use. in "dump", I tried to create a coredump during a lockup. "alltrace", "witness", "ps" also have been created during the lockup. "sysctl" contains the current settings. Can anyone recognize where the problem is coming from or is additional information needed? Jan