From nobody Fri Mar 25 15:16:13 2022 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2609B1A247E4 for ; Fri, 25 Mar 2022 15:16:57 +0000 (UTC) (envelope-from bsdlists@jld3.net) Received: from mail.jld3.net (mail.jld3.net [45.55.236.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KQ5Kg68xyz583X for ; Fri, 25 Mar 2022 15:16:55 +0000 (UTC) (envelope-from bsdlists@jld3.net) Received: from localhost (localhost [127.0.0.1]) by mail.jld3.net (Postfix) with ESMTP id 03E22415F2 for ; Fri, 25 Mar 2022 09:16:55 -0600 (MDT) X-Virus-Scanned: amavisd-new at jld3.net Received: from mail.jld3.net ([127.0.0.1]) by localhost (mail.jld3.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gn9X4-FhTkJ8 for ; Fri, 25 Mar 2022 09:16:52 -0600 (MDT) Received: from [172.21.35.238] (c-24-9-144-115.hsd1.co.comcast.net [24.9.144.115]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jld) by mail.jld3.net (Postfix) with ESMTPSA id 3D61B40124 for ; Fri, 25 Mar 2022 09:16:52 -0600 (MDT) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.jld3.net 3D61B40124 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.jld3.net 3D61B40124 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jld3.net; s=8d052f02dde2; t=1648221412; bh=OtGqmiH/C0IPzzQosuh5/418gXMKxt0AACZLIdyyVw8=; h=From:To:Subject:Date:Message-ID:MIME-Version:From; b=LgqXvQincMW2m89pv+lzgBE/oH+M6GQsJRlTvtVG+TzZytSMyb+2Ez8gRBm3kqHB6 VThaQr+tpKlLGRCqFAjSujPmqLG7m76LrGiInePb7OOFFpzNCb1nTST0XvjnXBjNp3 pV0NFhjC2G7AoKfW03QTFP/za4OmMlvxyjXDlrpA= From: "John Doherty" To: freebsd-fs@freebsd.org Subject: mirror vdevs with different sizes Date: Fri, 25 Mar 2022 09:16:13 -0600 X-Mailer: MailMate (1.13.2r5673) Message-ID: <95932839-F6F8-4DCB-AA7F-46040CFA1DE1@jld3.net> List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 4KQ5Kg68xyz583X X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=jld3.net header.s=8d052f02dde2 header.b=LgqXvQin; dmarc=pass (policy=quarantine) header.from=jld3.net; spf=pass (mx1.freebsd.org: domain of bsdlists@jld3.net designates 45.55.236.93 as permitted sender) smtp.mailfrom=bsdlists@jld3.net X-Spamd-Result: default: False [-3.75 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[jld3.net:s=8d052f02dde2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:45.55.236.93]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[jld3.net:+]; DMARC_POLICY_ALLOW(-0.50)[jld3.net,quarantine]; NEURAL_HAM_SHORT(-0.75)[-0.754]; MLMMJ_DEST(0.00)[freebsd-fs]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:14061, ipnet:45.55.192.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[24.9.144.115:received] X-ThisMailContainsUnwantedMimeParts: N Hello, I have an existing zpool with 12 mirrors of 8 TB disks. It is currently about 60% full and we expect to fill the remaining space fairly quickly. I would like to expand it, preferably using 12 mirrors of 16 TB disks. Any reason I shouldn't do this? Using plain files created with truncate(1) like these: [root@ibex] # ls -lh /vd/vd* -rw-r--r-- 1 root wheel 8.0G Mar 25 08:49 /vd/vd0 -rw-r--r-- 1 root wheel 8.0G Mar 25 08:49 /vd/vd1 -rw-r--r-- 1 root wheel 16G Mar 25 08:49 /vd/vd2 -rw-r--r-- 1 root wheel 16G Mar 25 08:49 /vd/vd3 I can first do this: [root@ibex] # zpool create ztest mirror /vd/vd{0,1} [root@ibex] # zpool list ztest NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT ztest 7.50G 384K 7.50G - - 0% 0% 1.00x ONLINE - And then do this: [root@ibex] # zpool add ztest mirror /vd/vd{2,3} [root@ibex] # zpool list ztest NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT ztest 23G 528K 23.0G - - 0% 0% 1.00x ONLINE - And FWIW, everything works as expected. But I've never constructed a real zpool with vdevs of different sizes and I don't know whether there might be any expected problems. I could just create a new zpool with new disks, but most of the existing data and most of the expected new data is in just two file systems and for simplicity's sake from the perspective of those users, it would be nicer to just make the existing file systems larger than to give them access to a new, different one. Any comments, suggestions, warnings, etc. much appreciated. Thanks.