Date: Wed, 15 Apr 2020 11:30:24 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Daryl Richards <daryl@isletech.net> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: zpool status question Message-ID: <1045079731.1.1586943024582@localhost> In-Reply-To: <7582e197-f18f-7137-fe9d-a21aabc4c989@isletech.net> References: <7582e197-f18f-7137-fe9d-a21aabc4c989@isletech.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <freebsd-fs@freebsd.org> Datum: zondag, 12 april 2020 21:26 Aan: freebsd-fs <freebsd-fs@freebsd.org> 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" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1045079731.1.1586943024582>