From owner-freebsd-questions@FreeBSD.ORG Wed Dec 17 20:41:09 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 219A7BD4 for ; Wed, 17 Dec 2014 20:41:09 +0000 (UTC) Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D89C1199A for ; Wed, 17 Dec 2014 20:41:08 +0000 (UTC) Received: by mail-ig0-f173.google.com with SMTP id r2so9452446igi.0 for ; Wed, 17 Dec 2014 12:41:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KvWSaKq/9tO6QzGxdITd6IUP4LnJjDQTL8W7xVWzklU=; b=ImR5dALpS9XszosNv8+387nHFMMIZrp95RmMmXcJBmR8jdEWoDW2HJGMqWsWjslweK B8s6eEso7cjpZOlAPI5mZPuhScWvTFXcZqy9mQ+BnPf9HR9vwG0IAVpITMWoNsl7gaTG UtTUmjFbtdbthLy1v/6UzHY2NgtKR9EWEDD/7EEJbbciRCX1oGBJak0aL1+BbL/LAolV oWj3vG+bkIPIH2AAggx/Dnmvh6v+m2T0N9R44nDn4V3H9ccpPB2Zg7ewMLnwhIsmIuaN 9B+fxoQvSZg9twXNc4Wwrlk+2HcWaIB77gt17L7pndGQ9EIdfY68MZqs048G/JMoATPp Ou8g== X-Received: by 10.43.142.13 with SMTP id jg13mr38351393icc.93.1418848868375; Wed, 17 Dec 2014 12:41:08 -0800 (PST) Received: from localhost.localdomain ([2601:7:6c80:6f00::a767]) by mx.google.com with ESMTPSA id vf6sm2771698igb.6.2014.12.17.12.41.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Dec 2014 12:41:07 -0800 (PST) Message-ID: <5491EA62.2080401@gmail.com> Date: Wed, 17 Dec 2014 13:41:06 -0700 From: jd1008 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Mike Tancsa , freebsd-questions@freebsd.org Subject: Re: zfs and 512/4096 sector sizes References: <5491E462.2020902@sentex.net> <5491E5A0.9090306@gmail.com> <5491E61B.9070505@bluerosetech.com> <5491E775.5010403@gmail.com> <5491E82D.8090105@sentex.net> In-Reply-To: <5491E82D.8090105@sentex.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2014 20:41:09 -0000 On 12/17/2014 01:31 PM, Mike Tancsa wrote: > On 12/17/2014 3:28 PM, jd1008 wrote: >>> Does the zpool clear command make it go away? > > > Nope, tried that :( > > # zpool clear tank1 ada11 > # zpool status > pool: tank1 > state: ONLINE > status: One or more devices are configured to use a non-native block > size. > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly configured > pool. > scan: resilvered 898G in 8h4m with 0 errors on Wed Dec 17 15:01:18 2014 > config: > > NAME STATE READ WRITE CKSUM > tank1 ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > ada12 ONLINE 0 0 0 > ada10 ONLINE 0 0 0 > ada6 ONLINE 0 0 0 > ada14 ONLINE 0 0 0 > raidz1-1 ONLINE 0 0 0 > ada11 ONLINE 0 0 0 block size: 512B > configured, 4096B native > > One last suggestion: dismantle the whole pool (i.e. remove the drives) and rebuild it fresh using only 512 byte sector drives. Whole adding the drives back in, one at a time, recheck the status after each add and see if the error status appears.