From nobody Mon Feb 27 18:05:43 2023 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 4PQT245qv3z3vQjr for ; Mon, 27 Feb 2023 18:05:48 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PQT234Df4z3vMs for ; Mon, 27 Feb 2023 18:05:47 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=ZF5U4xOp; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="e VKDqOL"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 936A85C0184 for ; Mon, 27 Feb 2023 13:05:46 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 27 Feb 2023 13:05:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm1; t= 1677521146; x=1677607546; bh=xQUhSLv0T4StWftU7qysFWLco5usYikIsQe yr54Wlf0=; b=ZF5U4xOpC8n8Uy1SdxZ8F940086c7RKdUazcFybOLCxKea4/fMn sE+W5BJHpTbGiSMHnZmihr6y0FhacNwVwCiHS6vxNLU24GiVxk5qYH9vGVQj15DV ZkuPhux6jmgKkhoyeFBgXcCF/PDUPKzdl6u2XlCnEBpHgiFjEgdV1peGxpusR7fF CfG43RlVzZcWymLP0lcg1DBymkxk1Gds8RwncNaLCJ0krTyHkwP/RecP/+Kenhua zcEbVYO5v+mtjSAGv4I/kvOcL8O9v2mkLB4dIwRsbWWxdQNVg5yKleyh7T47qOAG ZSwbQrpTm2NyyjjZ0mcpH+UmMrkLSJtYuDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1677521146; x= 1677607546; bh=xQUhSLv0T4StWftU7qysFWLco5usYikIsQeyr54Wlf0=; b=e VKDqOLYXZuZPI9X/aZ03D9bywvHEep9Yvs1pIkqy6BE6un2wNltYFBdtap/cMq3f lnr3YMT2/v0GpK6ToSyK3jeEEUKG+cr9i1XtixmWbiObkF3wSs9cx5WHk0lF1nPK fzGeONP8Ij9ys+PbTbHiWYBtL27jZ1IrHtcILHDBkGpWxgl0ANdQjv5u9TLd9Uao ngYk0wibYoeeTYKDTSM0I0XZW/Mov7vif4V4SVJE3T0VL2AZEJzjKvHpKf0P4BVT 9uf3rD4f9Oxc3ClXhXslgOqnSfFXscXfbhRy3yDB0AKCUOOOSIPL+fTMJlGAsdu1 Tup5IDVSM8xmc1lbTrmCQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeltddguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehttdertd dttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrght thgvrhhnpeevudffiedvffffgffhgeefjeefffdtieetheetkeefhfdvfefgtedtueehge ffueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehv ohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 27 Feb 2023 13:05:45 -0500 (EST) Date: Mon, 27 Feb 2023 18:05:43 +0000 From: void To: freebsd-fs@freebsd.org Subject: can another disk be added to a zfs stripe Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org 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; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-4.70 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PQT234Df4z3vMs X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N Hello fs@ On a 13-stable host I have a 13-stable bhyve guest. The vdisk is a 64GB zvol. In the guest, the filesystem is also zfs. I'd like to add another 64GB zvol to this zfs, and for the resulting zfs system (zroot) to remain a stripe. Is it simply a case of, within the guest (after booting the guest with an additional -d pointing to the unused-at-that-point zvol) and running 'zpool add zroot vtblk1' ? It's important the zpool remains a stripe not a mirror. Or is there a better way of doing this? tia, --