From owner-freebsd-fs@freebsd.org Wed Apr 15 09:30:27 2020 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CF1882B0AB4 for ; Wed, 15 Apr 2020 09:30:27 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 492HC62y3vz4Xwx for ; Wed, 15 Apr 2020 09:30:26 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Wed, 15 Apr 2020 11:30:24 +0200 (CEST) From: Ronald Klop To: Daryl Richards Cc: freebsd-fs Message-ID: <1045079731.1.1586943024582@localhost> In-Reply-To: <7582e197-f18f-7137-fe9d-a21aabc4c989@isletech.net> References: <7582e197-f18f-7137-fe9d-a21aabc4c989@isletech.net> Subject: Re: zpool status question MIME-Version: 1.0 X-Mailer: Realworks (503.2641.c9b12d36d36) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 492HC62y3vz4Xwx X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 194.109.157.24 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-0.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.888,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; NEURAL_HAM_LONG(-0.97)[-0.969,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[klop.ws]; URI_COUNT_ODD(1.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[24.157.109.194.list.dnswl.org : 127.0.15.0]; HAS_X_PRIO_THREE(0.00)[3]; IP_SCORE(-0.03)[ipnet: 194.109.0.0/16(-0.15), asn: 3265(-0.04), country: NL(0.03)]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; MIME_TRACE(0.00)[0:+,1:+,2:~] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Wed, 15 Apr 2020 09:30:28 -0000 Hi, Are you sure the new pool is not almost full. That creates a significant performance drop. Otherwise look at "zpool iostat" and "gstat" to see what the disks are doing. Ronald. Van: Daryl Richards via freebsd-fs Datum: zondag, 12 april 2020 21:26 Aan: freebsd-fs Onderwerp: zpool status question > > Hello list, > > I recently needed to add more storage to my pool and to get around the ashift problem of my old pool I made a new one on new drives and did a send->receive to copy my data. Everything went fine with the copy, but now when I do a zpool status, it takes about 15 minutes to show the status of the new pool. It takes about 5 minutes to show the first line (name of pool, then top level vdev), and then about 3 minutes per device after that. (4 drive raidz1). Everything shows ONLINE when done, no errors or timeouts show up in dmesg, nothing. It just takes a long time to display status.. Getting status of the other pools (zroot, and old array) is instantaneous. > > I'm just being overly cautious before I export the old array and import the new one as my main one.. I'm on FreeBSD 11.3-RELEASE > > Any ideas? Thanks! > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > >