From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 17:39:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F27E3106564A for ; Tue, 28 Dec 2010 17:39:31 +0000 (UTC) (envelope-from jyavenard@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B65918FC17 for ; Tue, 28 Dec 2010 17:39:31 +0000 (UTC) Received: by iwn39 with SMTP id 39so9653738iwn.13 for ; Tue, 28 Dec 2010 09:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=t8xpkEQq3SFV6CX4iH92enObGJ2IarUzLxf/qT956aM=; b=BX5liG5RpQPtoQjrXO/Y9r5lwtQRzNZd1Q/rlbEu1uvMPHoP2WNL/RwoaSHyWfICjt BGwsWuWeSBrUzMpxy7RCAHzq0qWd/mnbRdF3yPguR+7kojuRBh3XHnFwWCvtuabik4Hz v5HYKAkjA5yr61YqOGJFwAJSYjLateMUi1OvY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gzPhCFUajd6epQCi63KAFXZ3MtLzwMSmjRQZcPDhyH3wEFAWU/erJer7jUNXbnr8y7 JbmHin/1NN/W70IylKCB5rx3l5eCG7+lABTU8IKWN4Z223Lzu34GoByFxbPSyxNxvvvC heCdPH4TpkP/ZOQlp7xxSGG8nRT1Pzxh1LfRw= MIME-Version: 1.0 Received: by 10.42.178.9 with SMTP id bk9mr13764778icb.126.1293557971103; Tue, 28 Dec 2010 09:39:31 -0800 (PST) Received: by 10.42.220.70 with HTTP; Tue, 28 Dec 2010 09:39:31 -0800 (PST) In-Reply-To: References: <4D181E51.30401@DataIX.net> Date: Wed, 29 Dec 2010 04:39:31 +1100 Message-ID: From: Jean-Yves Avenard To: jhell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE: Kernel Panic 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: Tue, 28 Dec 2010 17:39:32 -0000 On 29 December 2010 03:15, Jean-Yves Avenard wrote: > # zpool import > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 15.11r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 15.94r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 16.57r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 16.95r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 32.19r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 32.72r 0.00u 0.03s 0% 2= 556k > load: 0.00 =A0cmd: zpool 405 [spa_namespace_lock] 40.13r 0.00u 0.03s 0% 2= 556k > > ah ah ! > it's not the separate log that make zpool crash, it's the cache ! > > Having the cache in prevent from importing the pool again.... > > rebooting: same deal... can't access the pool any longer ! > > Hopefully this is enough hint for someone to track done the bug ... > More details as I was crazy enough to try various things. The problem of zpool being stuck in spa_namespace_lock, only occurs if you are using both the cache and the log at the same time. Use one or the other : then there's no issue But the instant you add both log and cache to the pool, it becomes unusable= . Now, I haven't tried using cache and log from a different disk. The motherboard on the server has 8 SATA ports, and I have no free port to add another disk. So my only option to have both a log and cache device in my zfs pool, is to use two slices on the same disk. Hope this helps.. Jean-Yves