From owner-freebsd-questions@freebsd.org Sun Jun 12 22:14:14 2016 Return-Path: Delivered-To: freebsd-questions@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 A13E1AF19B8 for ; Sun, 12 Jun 2016 22:14:14 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9126921CC for ; Sun, 12 Jun 2016 22:14:14 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u5CMEDxx047862 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 12 Jun 2016 15:14:13 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: ZFS: Is 'zpool add' really irreversible? To: "Brandon J. Wandersee" References: <86shwiax38.fsf@WorkBox.Home> Cc: FreeBSD Questions From: Yuri Message-ID: <22e9b8aa-3171-f399-f3a8-b71eb92210f5@rawbw.com> Date: Sun, 12 Jun 2016 15:14:12 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <86shwiax38.fsf@WorkBox.Home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2016 22:14:14 -0000 On 06/12/2016 14:58, Brandon J. Wandersee wrote: > `zpool add` adds*virtual* devices to a*pool*, while `zfs attach` adds > physical devices to a mirrored device. So individual disks can be added > to and removed from mirrored virtual devices, but virtual devices cannot > be removed from a pool. Thank you for your answer. I see that ZFS is designed this way. But I can't say I like this part of ZFS design. Because this isn't a physical disk with the set size, but a combination of disks. People may reasonably want to remove some disks in some layouts, due to failures, etc, and ZFS just lacks the flexibility to do that. Thanks! Yuri