From owner-freebsd-current@FreeBSD.ORG Wed Jun 27 09:30:35 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 78FB616A469 for ; Wed, 27 Jun 2007 09:30:35 +0000 (UTC) (envelope-from freebsd-current@jschmidle.org) Received: from mxintern.schlund.de (mxintern.schlund.de [212.227.126.201]) by mx1.freebsd.org (Postfix) with ESMTP id 142F913C45B for ; Wed, 27 Jun 2007 09:30:35 +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 1I3Tr8-0006Zv-7U; Wed, 27 Jun 2007 11:30:34 +0200 Message-ID: <46822E39.2010507@jschmidle.org> Date: Wed, 27 Jun 2007 11:30:33 +0200 From: Jan Schmidle User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <46811756.105@jschmidle.org> <20070627070245.GB21749@garage.freebsd.pl> In-Reply-To: <20070627070245.GB21749@garage.freebsd.pl> 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: e7213a74a8a1130d0d28424fbf20585d Cc: Current@FreeBSD.org Subject: Re: 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: Wed, 27 Jun 2007 09:30:35 -0000 Pawel Jakub Dawidek wrote: > On Tue, Jun 26, 2007 at 03:40:38PM +0200, Jan Schmidle wrote: >> 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. > > Are you sure the disks are fine? Not 100%, but as the problem also shows up when I'm destroying pools, I don't think that there is a Problem. But I will check this. > >> 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. > > Backtraces would tell us if this is ZFS or not, can you include them? I will post a Backtrace as soon as I get a panic again. > >> "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? > The following were created during a panic. ----------------------------- db> show lockedvnods Locked vnodes db> ----------------------------- db> show alllocks Process 4144 (vdev:worker da2) thread 0xffffff0004b10000 (100230) exclusive sleep mutex zfs:vdev:geom:queue r = 0 (0xffffff000707d4b0) locked @ /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c:203 Process 4118 (spa_zio_intr_2) thread 0xffffff000456a680 (100172) exclusive sleep mutex zio_cache (UMA zone) r = 0 (0xffffff00cff40b70) locked @ /usr/src/sys/vm/uma_core.c:2257 Process 20 (swi2: cambio) thread 0xffffff00010ea9c0 (100017) exclusive sleep mutex Giant r = 0 (0xffffffff809db980) locked @ /usr/src/sys/cam/cam_xpt.c:7141 db> ----------------------------------------------------- ----------------------------------------------------- And these during lockup ----------------------------- db> show lockedvnods Locked vnodes 0xffffff0004a2dd90: tag syncer, type VNON usecount 1, writecount 0, refcount 2 mountedhere 0 flags () lock type syncer: EXCL (count 1) by thread 0xffffff000430c9c0 (pid 48) db> ----------------------------- db> show alllocks db> -----------------------------