From owner-freebsd-questions@FreeBSD.ORG Mon Jan 27 12:39:31 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06B533E9 for ; Mon, 27 Jan 2014 12:39:31 +0000 (UTC) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8D81A13E4 for ; Mon, 27 Jan 2014 12:39:30 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id w61so5210450wes.16 for ; Mon, 27 Jan 2014 04:39:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qikfrl+WJqmw6k6SURXNnL1EHQVyZ0bM6kGro5lNhJQ=; b=Tk33e6rNyl8TkPAbpZbfGCx3VIDYGg0AQhLcj02nB6x/mv3aH4NhQo9qG2MOko8wP4 Zey9cot4PdV+1iEVq2B/GZEnGvxEGfacB+1AJ6w9fYwoYMSUBo+f+pCg91F2Za2+okX4 7w6y4qElw4A698IzicW3+Z662EcGqRsB6LAjagB7qBP5Ga6dps3oP5Q4niEpfJ1F/sNo xldTNdD+BxEQ5xylDJgATUHqK5bovooQvEBEdmIihW9dCLfEBw/p3SXaVGgbNGc2CjB/ x/OrpoOyQxd3sPHch7UWGCfDoi5HFgnP5QbFaRTwXaMBjrpjVRhvN5B2DqgnAoR4TpCX RHLg== X-Received: by 10.194.179.69 with SMTP id de5mr20240207wjc.4.1390826368881; Mon, 27 Jan 2014 04:39:28 -0800 (PST) Received: from x220.optiplex-networks.com (81-178-2-118.dsl.pipex.com. [81.178.2.118]) by mx.google.com with ESMTPSA id n3sm27494513wix.10.2014.01.27.04.39.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Jan 2014 04:39:28 -0800 (PST) Message-ID: <52E6537F.8020907@gmail.com> Date: Mon, 27 Jan 2014 12:39:27 +0000 From: Kaya Saman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Subject: Re: ZFS confusion References: <52E40C82.7050302@gmail.com> <52E62DFF.3010600@gmail.com> <52E6463C.6090805@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 12:39:31 -0000 On 01/27/2014 12:12 PM, Trond Endrestøl wrote: > On Mon, 27 Jan 2014 11:42-0000, Kaya Saman wrote: > >> Many thanks everyone (Trond, Dennis, Steve)!! >> >> So RAIDz2 or 3 is going to be preferred per the advice given. >> >> Now I just need to figure out how to make that work best with my current 5 >> block of disks.... perhaps wait for a while then add some more disks in the >> mix then create the raidz(x) platform?? >> >> It would be really good if raidz could be expandable, ie by adding extra 'new' >> disks into the same vdev. > It's there! > > Try: zpool attach [new_member2 ...] > > Yep, though of course as I'm just testing with temp files currently I was unable to make it work: zpool attach test_pool /tmp/disk1 /tmp/disk6 cannot attach /tmp/disk6 to /tmp/disk1: can only attach to mirrors and top-level disks This is ok though as my block of 5 disks arrive tomorrow with the chassis arriving either tomorrow or day after that. Does 'attaching' create a hybrid raidz2/3 + 1 array or am I confusing again? Being familiar with raid 1 and 0, I know that the attach command will simply mirror a disk: zpool attach disk1 disk2 would create a raid1 mirror between the disks... is this the same principle or does the command function differently in raidz? Just checking out the man page gives this: zpool attach [-f] pool device new_device Attaches new_device to an existing zpool device. The existing device cannot be part of a raidz configuration. If device is not currently part of a mirrored configuration, device automatically transforms into a two-way mirror of device and new_device. If device is part of a two-way mirror, attaching new_device creates a three-way mirror, and so on. In either case, new_device begins to resilver immediately. -- unless things have been updated since my FBSD version? Regards, Kaya