From owner-freebsd-fs@freebsd.org Sun Jan 27 01:55:41 2019 Return-Path: Delivered-To: freebsd-fs@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 EB60414B8D8A for ; Sun, 27 Jan 2019 01:55:40 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4FE980FCF for ; Sun, 27 Jan 2019 01:55:39 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([5.144.193.252]) by mail.gmx.com (mrgmx101 [212.227.17.174]) with ESMTPSA (Nemesis) id 0Ldttv-1hW15q0fOl-00j2a1; Sun, 27 Jan 2019 02:50:21 +0100 Subject: Re: "zpool remove" failing To: jdelisle , freebsd-fs@freebsd.org References: From: Nikos Vassiliadis Message-ID: Date: Sun, 27 Jan 2019 03:50:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:s1iuqn2Pkw5sH2A4wGJTQn6/F6BjS8h9OMrt3nXpqbT2RwR0R2o XWzwjL3m+M2TSt0dIpErIL//mXv/Vk4qx91lrXsWUyzKyRvAvuUCEh/smpfdc6CUoUgYxfz TKahpNtZlam4pjio7yyvXWJcFJSBW089OzJdrpY/naanSn7by3dMTZdJMVIw9MtfbLT5qvY niijG4mMTngICBbblFfxg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:qEb4ZxE8ebM=:SHmXqFcmoLzFm87f344wPk JLnIBdmQu/9Sacdjq5sEQGytLYJd5zk5Ab6hUz2KHnNh93Ayba37Wqk723wo+uqAXAEKDLWw8 TpV9mkCp/AftlxD18wEexcXGtJjpK8sPo+YpKAledxWjQIcwQa30BEOKY61Nbak8soW9PLrAb z8aR/pFwD98Rd6+Pbt32tdpxh72dK7iJWyNfL6yb8ThueIJNjvZKV8muQd7W2EDIKNa61ylFy jCXRoFtd9OtiLJV8z8ixD62L45/IylQ1xyW3YVpTJ8yyCAVIhsdRJfnw005VMnV81nMbpvM28 ENhKJIE++iHKxJugflwaNkrVDFHr3I567Z12yDw2EeE6Gqk5liz12kwBlYQP2o4rqsYAYy9f8 0Lv32cIrI25/BhjqILPLxuAX4cQxXEczfun2Blz1iWDGQdHzW0sZWLuk/3kxtr7a2Iqg3Pd2r Tt4PbcnakWWSi9E84yb+j+47ZCwzmpN2l7BPL/XzwnC2g5Fuv/bvoywgOUuSkhn37ok+YHoBJ u9pPZ1EiVskLyRRsHtpMmiUUee3enfB5fV97OsoQxVtgsyLmArIyRQszBN8ZeCJBunR5MOJ/c qWZD4KieeX9gVBlYSZ0YHX3pBn5VenAJwnhuWrFOIy+Qp3AWME3OtlAhwq/1wRmPLst4qAAbX nDlry4jvN2PiJB16luak9jtdcDVeAUDarr4gOArgrmqk2b/LN9QkdxIatb8BQNPTwpsus4Utk AzjZ+dashOBxpAFFpQ70u3asEYZVR+xIkthT24Fpff2ZNLQHJ6UqJhj2CoRVC6yGPFvOmPQou 0fOuiS2SskcHZzdacGqtDEF7HLaM0VQWPJiuvOSlW1yE/ZEPnNbeJpcEDBTBKh8te+eXwnPTg cDHx56Tq91gYf6f8jDVHw1aoT8lvf7pYpwOtAnAehycfcTGdxb4FG5zfEJ5YIo X-Rspamd-Queue-Id: B4FE980FCF X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of nvass@gmx.com designates 212.227.17.22 as permitted sender) smtp.mailfrom=nvass@gmx.com X-Spamd-Result: default: False [-3.37 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmx.com]; R_SPF_ALLOW(-0.20)[+ip4:212.227.17.0/27]; MX_GOOD(-0.01)[mx01.gmx.net,mx00.gmx.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.55)[-0.550,0]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[22.17.227.212.list.dnswl.org : 127.0.3.1]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmx.com]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[252.193.144.5.zen.spamhaus.org : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.984,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[gmx.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-0.43)[ip: (-3.63), ipnet: 212.227.0.0/16(-0.68), asn: 8560(2.17), country: DE(-0.01)]; RWL_MAILSPIKE_POSSIBLE(0.00)[22.17.227.212.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2019 01:55:41 -0000 On 1/19/19 6:39 PM, jdelisle wrote: > I'm grasping at straws here, but could this functionality be incomplete in > 11.2-RELEASE? Would connecting my disks to a 12.0-RELEASE system help? > > It's easy for me to do that, but is it safe to move them to a 12.0-RELEASE > system, run the "zpool remove", then move them back to my 11.2-RELEASE > system? > > Is there any diagnostic output I could share that would help? > > I'm still confused by the error I'm getting from "zpool remove".. I'm > attempting to remove a top-level mirror vdev, and they're all the same > sector-size. ZFS has used stripesize to configure the newly added mirror. It does have a different sector size and this is why it cannot remove it anymore. If you examine the pool with zdb you can confirm it yourself. Sorry for the bad news... Nikos