From owner-freebsd-fs@freebsd.org Tue Jul 14 18:19:10 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9B449A1744 for ; Tue, 14 Jul 2015 18:19:10 +0000 (UTC) (envelope-from chris@stankevitz.com) Received: from mango.stankevitz.com (mango.stankevitz.com [208.79.93.194]) by mx1.freebsd.org (Postfix) with ESMTP id B6BFABCB for ; Tue, 14 Jul 2015 18:19:10 +0000 (UTC) (envelope-from chris@stankevitz.com) Received: from Chriss-MacBook-Pro.local (209-203-101-124.static.twtelecom.net [209.203.101.124]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mango.stankevitz.com (Postfix) with ESMTPSA id A9CAC6F8; Tue, 14 Jul 2015 11:19:09 -0700 (PDT) Message-ID: <55A552A0.3010408@stankevitz.com> Date: Tue, 14 Jul 2015 11:19:12 -0700 From: Chris Stankevitz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Freddie Cash CC: FreeBSD Filesystems Subject: Re: Offline/online a drive from a mounted RW RAIDZx pool: resilver needed? References: <55A4461F.6020308@stankevitz.com> <55A53BE2.7060609@stankevitz.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 18:19:10 -0000 On 7/14/15 9:46 AM, Freddie Cash wrote: > If nothing is written to the pool (or, at least that specific vdev) > while the drive is removed, then the metadata on the drive will match > the pool, and it can be onlined without a resilver. > > If only a little bit of data has been written, and a short bit of time > has passed, ​ > ​then the drive will only need to sync (resilver) that changed data to > the drive. > > If a lot of data has been written, or a long time has passed (not sure > what qualifies as "long", maybe until the last txg synced to the disk is > no longer in the txg history of the pool?), then the entire drive will > be resilvered. > > Or, something along those lines. That's what I've observed by doing > various tests (offline drive, pull drive, write to pool, online drive; > or offline drive, replace with new one, start resilver, new drive > dies, stick in old drive, online it, wait for resilver; and other > scenarios). Freddie, Thank you. That certainly agrees with what I experienced. You can imagine my terror when I yanked the wrong drive... and my fear/confusion when the drive did not resilver as I expected. Chris