From owner-freebsd-fs@freebsd.org Thu Jan 28 10:39:10 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BEE68A70DE1 for ; Thu, 28 Jan 2016 10:39:10 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 80CD115AE for ; Thu, 28 Jan 2016 10:39:09 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.186] (izaro.sarenet.es [192.148.167.11]) by proxypop01.sare.net (Postfix) with ESMTPSA id 91E959DDE1E; Thu, 28 Jan 2016 11:29:42 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: ZFS bug: zpool expandz says 16.0E, clearly wrong From: Borja Marcos In-Reply-To: Date: Thu, 28 Jan 2016 11:29:41 +0100 Cc: freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0614ACAB-DFF0-4CBE-8AA1-4EAE4668DBA9@sarenet.es> References: To: Marie Helene Kvello-Aune X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 10:39:10 -0000 > On 26 Jan 2016, at 17:17, Marie Helene Kvello-Aune = wrote: >=20 > I've stumbled across a curiosity with my zpool. The command 'zpool = list' > states that the EXPANDZ property/value is 16.0E. This is clearly = incorrect. > :) Or not, maybe your encryption+compression has triggered a Shannon = Singularity! ;) > The pool consist of a single RaidZ2 vdev of 6 drives, and two cache = drives. > No log device. Executing 'zpool list -v' shows that each member of the > RaidZ2 has an 'EXPANDZ' value of '-', as expected. But the RaidZ2 = itself, > and the pool, has a EXPANDZ value of 16.0E. Now, seriously. I=E2=80=99ve seen odd size reports for cache drives = before. Can you try running =E2=80=9Czdb=E2=80=9D and see where the wrong size is reported? Maybe detaching and reattaching the cache drives from the pool might = help, in case something related to the cache drives is creating the confusion. Borja.