Date: Tue, 9 Apr 2019 23:04:23 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Karl Denninger <karl@denninger.net>, freebsd-stable@freebsd.org Subject: Re: Concern: ZFS Mirror issues (12.STABLE and firmware 19 .v. 20) Message-ID: <c96e31ad-6731-332e-5d2d-7be4889716e1@FreeBSD.org> In-Reply-To: <f87f32f2-b8c5-75d3-4105-856d9f4752ef@denninger.net> References: <f87f32f2-b8c5-75d3-4105-856d9f4752ef@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/04/2019 22:01, Karl Denninger wrote: > the resilver JUST COMPLETED with no errors which means the ENTIRE DISK'S > IN USE AREA was examined, compared, and blocks not on the "new member" > or changed copied over. I think that that's not entirely correct. ZFS maintains something called DTL, a dirty-time log, for a missing / offlined / removed device. When the device re-appears and gets resilvered, ZFS walks only those blocks that were born within the TXG range(s) when the device was missing. In any case, I do not have an explanation for what you are seeing. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c96e31ad-6731-332e-5d2d-7be4889716e1>