From nobody Mon Feb 27 23:11:11 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 4PQbpX3rDDz3tJ3q for ; Mon, 27 Feb 2023 23:11:16 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 4PQbpW2N5Rz3vpZ for ; Mon, 27 Feb 2023 23:11:15 +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=bSEgbtmZ; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="A+wF/dKe"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.29 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2DF975C0113 for ; Mon, 27 Feb 2023 18:11:14 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 27 Feb 2023 18:11:14 -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:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1677539474; x=1677625874; bh=bTDBKpsnAb 1XDsVda3PwJViQKYZ8mZMjXIfp4Nf/eI0=; b=bSEgbtmZRjC5lLuBNppYPrY9m5 GQhZo4groT7kVrGrHMjJd7xR8lh6aEfj7/EJ3PItKoztTvQ/c8xHZUyRXDNU8UYm n6pgr79xUotydtAAvs1VkOATkh55vuErFIHN7MvaZ5dheGMkIrLy0Vjjtv7Fw6hp 6/mihm2ERUaZ+oN2Zh4yelSMDcyfPHspExbd62ZwLDzGYghtKHOOOqu1NvGefH9j xQjdhrNyuZDfKt7IotcK8AzIsoS75h8wfS0mNcpQ2qq9cmJ4cWGwwUSdr9ARCE/W RTm2bdqzyeIIIX5qZgIPznRX0Uuu7eqfc9Cs/C/R7nSEqD8M4PyzT0C5jG0w== 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:in-reply-to:message-id :mime-version:references: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=1677539474; x=1677625874; bh=bTDBKpsnAb1XDsVda3PwJViQKYZ8 mZMjXIfp4Nf/eI0=; b=A+wF/dKeFKlstXDtwEVKRjjZKQlYzg7XBlzqZGjuZqEb pM4ibyItQ1yFeVwOa8wXi7JnTWF7Fzp1bHh+7zyJXeYXa7DhWnB/jMnF4K0BABXL +iasGFax9WyRZTbq9ApphOODRHOS/DUXnWyk/hU8owOMWPJm7i7KiaNSP1Dk39vf 1Tx3NZcWKSS0Np8UMnuT3aASFFkNO87fx2dHYikJ0SqMXHzhmqE6ulh3gplyuxlJ NEdeeq5IWHXjXEWPFHHRgKiO5sGl9x2UcXbVJuKS7LMwv++xflJyyreT8+6VqXqq hklbP+QJFyi1VCaBG1wLbWs/B6ACXn5W+IHCyxt3FQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeluddgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 27 Feb 2023 18:11:13 -0500 (EST) Date: Mon, 27 Feb 2023 23:11:11 +0000 From: void To: freebsd-fs@freebsd.org Subject: Re: can another disk be added to a zfs stripe Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org References: 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 In-Reply-To: X-Spamd-Result: default: False [-4.57 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.972]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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: 4PQbpW2N5Rz3vpZ X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 03:52:46PM -0700, Alan Somers wrote: >Yes, that should work. But why would you want to? If it's just a >matter of adding space to the guest, you'd be better off simply >enlarging the zvol. I wondered about that. But how would the guest handle it? Would I not have to tell the zfs guest that there's more space, or is it automatic? --