From owner-freebsd-current@FreeBSD.ORG Mon Sep 16 12:29:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5F8B8535 for ; Mon, 16 Sep 2013 12:29:46 +0000 (UTC) (envelope-from supportme@ukr.net) Received: from fmd1s.ukr.net (fmd1s.ukr.net [195.214.192.43]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0BEA52981 for ; Mon, 16 Sep 2013 12:29:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-Id:Cc:To:Subject:From:Date; bh=A2O5G2rETBDFvaRTFDrZ+xuYjTCyBLHg3Zv52GAjTXs=; b=L4O57rhcV0QPbeTHzswizoXZt8wcXOnHCsQgsAETxlmu5r8btW45sPzA6EU9ud9H6R0wjFTIHwivUj2Tivp4jj9CoD5anTZ+lRZxFHuBELL3HsZGJk2xxqQGI8tMClCbKLOA9k7OBDIj5zGIcJ7878Kb0bslZAz0zHZJ6Adqr8w=; Received: from [10.0.10.112] (helo=fmst-6.ukr.net) by fmd1s.ukr.net with smtp ID 1VLXvz-000Dqb-6k for freebsd-current@freebsd.org; Mon, 16 Sep 2013 15:29:43 +0300 Date: Mon, 16 Sep 2013 15:29:41 +0300 From: Dmitriy Makarov Subject: Re[3]: ZFS secondarycache on SSD problem on r255173 To: Steven Hartland X-Mailer: freemail.ukr.net 5.0 Message-Id: <1379334340.567465877.0b1lli6r@fmst-6.ukr.net> In-Reply-To: <1379333192.127359970.ma5jnbc5@fmst-6.ukr.net> References: <1379069539.824504225.3b9xwugp@fmst-6.ukr.net> <74C1D072-77BB-4D6C-B78F-C8D2731FA0CF@sarenet.es> <1379333192.127359970.ma5jnbc5@fmst-6.ukr.net> MIME-Version: 1.0 Received: from supportme@ukr.net by fmst-6.ukr.net; Mon, 16 Sep 2013 15:29:42 +0300 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Justin T. Gibbs" , freebsd-current@freebsd.org, Borja Marcos X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 16 Sep 2013 12:29:46 -0000 And have to say that ashift of a main pool doesn't matter. I've tried to create pool with ashift 9 (default value) and with ashift 12 with creating gnops over gpart devices, export pool, destroy gnops, import pool.  There is the same problem with cache device. There is no problem with ZIL devices, they reports  ashift: 12        children[1]:             type: 'disk'             id: 1             guid: 6986664094649753344             path: '/dev/gpt/zil1'             phys_path: '/dev/gpt/zil1'             whole_disk: 1             metaslab_array: 67             metaslab_shift: 25             ashift: 12             asize: 4290248704             is_log: 1             create_txg: 22517 Problem with cache devices only, but in zdb output tere is nothing at all about them. --- Исходное сообщение --- От кого: "Steven Hartland" < killing@multiplay.co.uk > Дата: 16 сентября 2013, 14:18:31 Cant say I've ever had a issue with gnop, but I haven't used it for some time. I did have a quick look over the weekend at your issue and it looks to me like warning for the cache is a false positive, as the vdev for cache doesn't report an ashift in zdb so could well be falling back to a default value. I couldn't reproduce the issue for log here, it just seems to work for me, can you confirm what ashift is reported for your devices using: zdb Regards Steve ----- Original Message ----- From: "Borja Marcos" < --- Дмитрий Макаров --- Дмитрий Макаров