From owner-freebsd-fs@FreeBSD.ORG Mon Jun 22 23:13:30 2015 Return-Path: Delivered-To: freebsd-fs@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7FA165FF for ; Mon, 22 Jun 2015 23:13:30 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 471BC655 for ; Mon, 22 Jun 2015 23:13:29 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id t5MNDRhR023038; Mon, 22 Jun 2015 18:13:27 -0500 (CDT) Date: Mon, 22 Jun 2015 18:13:27 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Quartz cc: freebsd-fs@freebsd.org Subject: Re: ZFS pool restructuring and emergency repair In-Reply-To: <558883CD.3080006@sneakertech.com> Message-ID: References: <5584C0BC.9070707@sneakertech.com> <5587BC96.9090601@sneakertech.com> <20150622115856.GA60684@neutralgood.org> <55887BE8.2090305@sneakertech.com> <55888235.5000100@infracaninophile.co.uk> <558883CD.3080006@sneakertech.com> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Mon, 22 Jun 2015 18:13:27 -0500 (CDT) 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: Mon, 22 Jun 2015 23:13:30 -0000 On Mon, 22 Jun 2015, Quartz wrote: >> Although in one of Matt Ahrens talks at BSDCan he spoke of plans to >> change this. Essentially you'ld be able to offline a vdev, and a >> background process (like scrub) would copy all the data blocks from that >> device to elsewhere in the pool. Once finished, the devices making up >> the vdev could be physically removed. > > Oh, that would be nice. Was there a timeline guesstimate for when that would > be implemented, or was it more a "maybe someday" thing? This has been planned for perhaps 8 years already. Still in the original status. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/