From owner-freebsd-fs@FreeBSD.ORG Mon Jan 9 12:09:44 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8ECD3106566B for ; Mon, 9 Jan 2012 12:09:44 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id 202AE8FC0C for ; Mon, 9 Jan 2012 12:09:44 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0M6c40-1SgIsd0XLw-00wWtK; Mon, 09 Jan 2012 13:09:43 +0100 Message-ID: <4F0AD906.5080507@brockmann-consult.de> Date: Mon, 09 Jan 2012 13:09:42 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20111205220715.GA36072@freebsdbox.adamsnet> <4EDDE954.9020709@gmail.com> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:X64QXhP0j+GpVJ/vyvW2jPUJQ4mTv0uWD7DtHnJ+8Ro zP2ZP54ghSdGzoq/qhbi9DAMt+vIxwxYreokZ58HZmrqV9qSFv jmc4+08GrcwF8FD3xUShvVNQITl/GN2rBWjAFPPXwFIIwu5ah9 7yrkdATA38iS+Sw6OZ11bHSUF+4FHSW3KpH+ARXulSBMmKpsa4 m1IdsONNXIp1/Yz94sFd3nzoyQNsTx4wC1qqQCFry+f0Z5xZ0A niNBEvoyOXKcQ9lvNX+Rk7c/E4njYvJthkIyJJZGT664DlUlZ9 KgCYlCu51gPwegzOjeiggVNAf9IhE5ticArzGcN7UF2tBN2Vk/ xhBZSmXX/pL56TxbVCokEtExH9FONeHr2AbYwNz2D Subject: Re: weird bug with ZFS and SLOG X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 12:09:44 -0000 On 12/06/2011 03:22 PM, Adam Stylinski wrote: > On Tue, Dec 6, 2011 at 5:07 AM, Volodymyr Kostyrko wrote: > > ... > Actually my pool was created on 7.2 and has been updated every release, is > that a factor? I think the answer is yes. Today I caused the same thing you guys did, with a log that wouldn't go away. I always did the same thing on the main system, with no issues (removing/replacing the log). But today for the first time, I wanted to remove the log from the backup system, and it caused/revealed that problem. I think the relevant difference between the two systems is that I destroyed and recreated the main system's zpool after I upgraded to 8-STABLE and zpool v28 (still zfs version 4). The backup system was upgraded from v15 to v28. old: zpool v15 zfs v4 new: zpool v28 zfs v4 And now to fix it, I am moving and destroying the pool. (to zpool v28 zfs v5) It is easy to just offline the device and remove it, but I want to be sure there is nothing else broken in there. For example, if I attach a mirror to the log now, it triggers a resilver that does not show which disk is resilvering in zpool status, and says it will take 25 hours, even though the 8GB SSD log obviously doesn't need that long (and replacing a pool disk doesn't either). And zdb shows more than just the log disk, but all slices with the same physical disk with "resilvering: 1". That is not extremely serious, but undesirable. > I did manage to do this in a VM, so in any case we'll > probably have to do something that involves zdb. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de --------------------------------------------