From owner-freebsd-stable@freebsd.org Sun Apr 7 15:36:46 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BAE91558EEF; Sun, 7 Apr 2019 15:36:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 E390B9493B; Sun, 7 Apr 2019 15:36:43 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0AB95210F2; Sun, 7 Apr 2019 11:36:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 07 Apr 2019 11:36:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:cc:subject:message-id:mime-version:content-type; s= fm2; bh=zGCT3CmTqGVetzGIOhw9+7WNGXlGtzmRRN3f2L3hir0=; b=rvVQwxiy /6iuy4UT5mJ4m1DKrN4kYnmAMhyF9Vf1SiwX59TdN7FurJC8mO9uKxBV1SMmupKO CD5GCMck/PvWtXqCf1eNVXjVz6YK3PddO/0na+kp3GZKKib84gU1GvLXqbCUiKAH nBbI3X4vyflmrYvdrSmF0btZjUJRLaqRlxWJAHohh6nxqaxij/1Jd/RWuH3IlE5R cC5UUqNw0dqA9g1J4ud8dKkjwp3tjtynJOY8uVTYl+h/lNAC+JjA9mtLgVSWvaAg oa2BeFBzLRJLAFUAxm4RrdvbOYjtokYvUZ/dleCNTRj/Jh1mzdi6uyQS79UhaEdN iBCVTs8aihGpNQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=zGCT3CmTqGVetzGIOhw9+7WNGXlGt zmRRN3f2L3hir0=; b=blmSv60FoYttUdqu8MIev5VKQH6cRYgaJgaT2CeE4PR/N iutP4nr2YUA587XGq3G+sdmxbOfyKJfc/3elMsXtzoh3MqMVxKC0T7rbOYlkrYHP Y4XIJkLTXmVaJVoYWXVeiePMpas8XndxtqoSnSG+42pa6v3eZCuJQ03WI/YN3wP9 auIKQln52M16CMu/Du/pAvkee+VQW2/xFB5hg4VsOrR/rM823lZUhtGQoyTc2uCw dPTm7I7Xu6JX8ttVpaVFS/IJeqmAdeaBeHl8ZxlJoxUmJpNx4Tt2qQ9O1iWXWC8A 08vFAmWKHrFNVBOlToFcL+p33WDss7DnyBb+QAm9A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddugdekleculddtuddrgedutddrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvf fukfggtggufgesghdtreertdervdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgv tghhqdhlihhsthhsseiihiigshhtrdhnvghtqeenucfkphepkedvrdejtddrledurddutd dunecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthhdqlhhishhtshesiiihgihsthdr nhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from rpi3.zyxst.net (rpi3.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 2F4FCE45F3; Sun, 7 Apr 2019 11:36:42 -0400 (EDT) Date: Sun, 7 Apr 2019 16:36:40 +0100 From: tech-lists To: freebsd-fs@freebsd.org Cc: freebsd-stable@freebsd.org Subject: about zfs and ashift and changing ashift on existing zpool Message-ID: <20190407153639.GA41753@rpi3.zyxst.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: E390B9493B X-Spamd-Bar: --------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=rvVQwxiy; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=blmSv60F; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.27 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-9.18 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[zyxst.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; MX_GOOD(-0.01)[in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; IP_SCORE(-3.49)[ip: (-9.45), ipnet: 66.111.4.0/24(-4.59), asn: 11403(-3.35), country: US(-0.06)]; RCVD_IN_DNSWL_LOW(-0.10)[27.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2019 15:36:46 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I have this in sysctl.conf on a desktop machine (12-stable): vfs.zfs.min_auto_ashift=3D12 this has not always been there. I guess the zpool pre-dates it. I only noticed it because have recently had to replace a disk in its zfs array when I saw this: % zpool status pool: storage state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Sun Apr 7 03:09:42 2019 3.46T scanned at 79.5M/s, 2.73T issued at 62.8M/s, 3.46T total 931G resilvered, 78.94% done, 0 days 03:22:41 to go config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 replacing-0 ONLINE 0 0 1.65K ada2 ONLINE 0 0 0 ada1 ONLINE 0 0 0 block size: 512B configured, 4= 096B native ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 What I'd like to know is: 1. is the above situation harmful to data 2. given that vfs.zfs.min_auto_ashift=3D12, why does it still say 512B configured for ada1 which is the new disk, or.. 3. does "configured" pertain to the pool, the disk, or both 4. what would be involved in making them all 4096B 5. does a 512B disk wear out faster than 4096B (all other things being equal) Given that the machine and disks were new in 2016, I can't understand why z= fs didn't default to 4096B on installation thanks, --=20 J. --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAlyqGPwACgkQs8o7QhFz NAU4zQ//cpkfnOep4ZM6n3HiNrBZ6Jqcfam8VYoow7X3roQm5JoSiIj9lYd0BAOF qupSwygvQRx2L14MnfPfCHcIcJAi+Oj/hsT6t3GxyNnK5wcQr6ng24BQ0x6dnzgh OU2kxq0jn0S/NIs09IcAa4zaeXqxCcnIwHbyPAD8ilU261nibdrnqW+bzLUZarYj SXbap9G5MWA6U1mBZsmGdVRZpyGAM/G1xQ5BT+ovNezSr2ssABoAtSy9DsQnbgmU plpq697kZWRokNcV25ASlyK5+nC71RawxDQ/YnMAVU0ZWItAWUkyI1LLjXahZtDV lmBfNMcP79iAcxJvfca9tp4sESlUG3eV/kHnm6kgD9XLDXDyu7jQfpfbgpB+4a8o 0O/BzXpNQD78E3W4zHaKBVswman+KHbbzcXUGc6Icm2sS6BTExXJYFMtjZI9Zt9g ho13EYQWAAVRX0FZOGXkn4xFAOVU4o3D4WHdiDjS9bINNVY5h8Y0/f/L1Uv9I4CB S64UfdkqLFaI2YSikZjtwnRr7vhdwovRdErILkZCp0UrC0GnqWRknosd+Kc+1wQT 4/djfaI6W9aUWUlDSQfml8MW03Fm7BtISvCTzg/nAUm4PnNmxkT025FrR12LD/9Y 5heGKN/1HNTbEWu5uL2cGM85yA1nHAqBomdDPYzdHkRzUc+Fiu0= =PrOZ -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--