From owner-freebsd-fs@freebsd.org Mon Jan 11 11:45:05 2016 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 707B7A6C0AF for ; Mon, 11 Jan 2016 11:45:05 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0AA0514C1 for ; Mon, 11 Jan 2016 11:45:04 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x232.google.com with SMTP id f206so209261694wmf.0 for ; Mon, 11 Jan 2016 03:45:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=p9fn3gIGhovpXm0N3YBHXn5HvSd9LEW2+2YxQ0RBI3o=; b=npqWY38HgH2WbXupErZBG6IVqmcNnmy/ivfcE1o6xObfzT2gOcij+pOSerWjCYxTLV tCT2SxdSOYamAM1IfCl0IClEM0uRgyz8oQz40O78TuHCWIxvoGTY/pjovhKcRVJqCtKG FT4bN9Oa0WfN/TjNycwY0EtJs0D2V0G6dlI0THiQrD9z1xEAzqBUhPYo/o7/LdczHQtM CnBb874hoKuLT6KpykGzBollzfiLUtQVG6GaeTs3NeDvR5AHsbbkHOOlBbZYtlsZXoji TdD4Vpa/g/F3mDIyD8BwKozuAUdMqnEHgHox4aEPkfK7h0O53CT4GUtxQuiRJkLP5zk0 WKDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=p9fn3gIGhovpXm0N3YBHXn5HvSd9LEW2+2YxQ0RBI3o=; b=ivhSX74+MG3ot54YAyIUBSl69k473knTro0Ht1qzijgtKv6GamvLlEprhQGq4SCWbI /X/mcH4mgFP3nCc3+OoDtNyT6DHzu4DfsXwD8Y4LusOmvDETed3dRBMN1nsoR5al4E3F CTy9IlKcn+qbeL5YN959FT8QKzyOB9FEs7Un7a7cKnmxiy5imQSa1NjdkPYr8Ehta5rM 9B6nv7nC4cCqfPp61SgZpt9drJsTeLBNi+nF2Gm0PXN3SGfBEjx8eJIDd1tJuEdMjDuE rSIysTS3xRavL1NKhUBaLCe6EwFlmaBU0p9sevKgvnkTl753FSg6WUOMXLLxXPeofw7I aBJA== X-Gm-Message-State: ALoCoQklbI6nRCsf2Tp0Py/loYjbeaTLVVbgqLqpzKpJ2zBzhapqtz2aSZwHbI+4GdL0+nPWMOcC0QmYhiky+Ib4m5ZGMoM04w== X-Received: by 10.28.170.139 with SMTP id t133mr13827445wme.50.1452512702025; Mon, 11 Jan 2016 03:45:02 -0800 (PST) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id bg10sm119080370wjb.46.2016.01.11.03.45.00 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jan 2016 03:45:00 -0800 (PST) Subject: Re: Question on gmirror and zfs fs behavior in unusual setup To: freebsd-fs@freebsd.org References: From: Steven Hartland Message-ID: <569395CC.6060104@multiplay.co.uk> Date: Mon, 11 Jan 2016 11:45:16 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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, 11 Jan 2016 11:45:05 -0000 On 11/01/2016 11:18, Octavian Hornoiu wrote: > I currently have several storage servers. For historical reasons they have > 6x 1TB Western Digital Black SATA drives in each server. Configuration is > as follows: > > GPT disk config with boot sector > /dev/ada0p1 freebsd-boot 64k > /dev/ada0p2 freebsd-swap 1G > /dev/ada0p3 freebsd-ufs 30G > /dev/ada0p4 freebsd-zfs rest of drive > > The drive names are ada0 through ada5. > > The six drives all have the same partition scheme. > - They are all bootable > - Each swap has a label from swap0 through swap5 which all mount on boot > - The UFS partitions are all in mirror/rootfs mirrored using gmirror in a 6 > way mirror (The goal of the boot and mirror redundancy is any drive can die > and I can still boot off any other drive like nothing happened. This > partition contains the entire OS. > - The zfs partitions are in RAIDZ-2 configuration and are redundant > automatically. They contain the network accessible storage data. > > My dilemma is this. I am upgrading to 5 TB Western Digital Black drives. I > have replaced drive ada5 as a test. I used the -a 4k command while > partitioning to make sure sector alignment is correct. There are two major > changes: > > - ada5p3 is now 100 G > - ada5p4 is now much larger due to the size of the drive > > My understanding is that zfs will automatically change the total volume > size once all drives are upgraded to the new 5 TB drives. Please correct me > if I'm wrong! The resilver went without a hitch. Correct you just need to ensure that autoexpand is enabled on the pool e.g. zpool set autoexpand=on tank > My concern is with gmirror. Will gmirror grow to fit the new 100 G size > automatically once the last drive is replaced? I got no errors using insert > with the 100 G partition into the mix with the other 5 30 G partitions. It > synchronized fine. The volume shows as complete and all providers are > healthy. I'm not sure with gmirror 100% but the following seems to detail what you want: https://lists.freebsd.org/pipermail/freebsd-questions/2007-August/156466.html > > Anyone with knowledge of gmirror and zfs replication able to confirm that > they'll grow automatically once all 6 drives are replaced or do I have to > sync them at existing size and do some growfs trick later? > > Thanks! > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"