From owner-freebsd-questions@FreeBSD.ORG Wed Dec 17 20:28:39 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 BDFF9324 for ; Wed, 17 Dec 2014 20:28:39 +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 822BC1726 for ; Wed, 17 Dec 2014 20:28:39 +0000 (UTC) Received: by mail-ig0-f173.google.com with SMTP id r2so9398000igi.12 for ; Wed, 17 Dec 2014 12:28:39 -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=kEqkWGAt4EwQPxGgkzGMDO7YBd7Ub1pNztiP4qlOMKg=; b=fWe9AzhokASMmSyqBaUu/m6E/vblf453FYAXC4OKfiZ9VRYhFUKMynKPlWSjYNY6Wb 2lO3zFCsm9u1gbAnkB/LL1rzzF+qPMTCrgGse6oFpntTi6lvxD0fbAlesU+KQH4RvsLE NfsDUg/1fku1wytq0aBg9cCTJ8wBG14G375ZxeUXjnz5dRTMeF2ZYNSz29EezPwvGlmo AkdjF8DE/vB+V1eyTQAvTSdNcbCiEI6eanj+0ypu++0Qr49fAvG06bV/PFyQlGvsBhRP d9y90UpM9MDYWYoiFRXUCsD409Tf5ZpCbDwi49yRIVr3znsE6pytRYY96D5YWIFPTD1W iCwA== X-Received: by 10.50.70.2 with SMTP id i2mr10116455igu.46.1418848118998; Wed, 17 Dec 2014 12:28:38 -0800 (PST) Received: from localhost.localdomain ([2601:7:6c80:6f00::a767]) by mx.google.com with ESMTPSA id j139sm2093732ioe.20.2014.12.17.12.28.38 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Dec 2014 12:28:38 -0800 (PST) Message-ID: <5491E775.5010403@gmail.com> Date: Wed, 17 Dec 2014 13:28:37 -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: 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> In-Reply-To: <5491E61B.9070505@bluerosetech.com> Content-Type: text/plain; charset=utf-8; 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:28:39 -0000 On 12/17/2014 01:22 PM, Darren Pilgrim wrote: > On 12/17/2014 12:20 PM, jd1008 wrote: >> >> On 12/17/2014 01:15 PM, Mike Tancsa wrote: >>> status: One or more devices are configured to use a non-native block >>> size. >>> Expect reduced performance. >> The status report does not identify the offending drive, >> so if you remove the drive (instead of replacing it), >> do you still get the same status report? > > It shows the sector size mismatch for ada11 in the vdev configuration > list. > > Does the zpool clear command make it go away? > > Manpage says: *zpool* *clear* [*-F* [*-n*]]/pool/ [/device/] Clears device errors in a pool. If no arguments are specified, all device errors within the pool are cleared. If one or more devices is specified, only those errors associated with the specified device or devices are cleared. *-F* Initiates recovery mode for an unopenable pool. Attempts to discard the last few transactions in the pool to return it to an openable state. Not all damaged pools can be recovered by using this option. If successful, the data from the discarded transactions is irretrievably lost. *-n* Used in combination with the*-F* flag. Check whether discard- ing transactions would make the pool openable, but do not actually discard any transactions. So, be sure to specify ada11