From nobody Tue Feb 28 14:09:06 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 4PQzkb61Tmz3vVHr for ; Tue, 28 Feb 2023 14:09:11 +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 4PQzkZ5Rfnz4K0l for ; Tue, 28 Feb 2023 14:09:10 +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=gjD16u6S; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=dTuvBJgF; 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 compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 150555C009C for ; Tue, 28 Feb 2023 09:09:09 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 28 Feb 2023 09:09:09 -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=1677593349; x=1677679749; bh=QsMJVdcalh Dz2s9tQRNIjHHjuRF5DTS5XYtiESt55Ug=; b=gjD16u6SJy6gNbqZajlig4K/ER cRAn3D00tkqwzaUjW1v3396I/KPB8JVYH9HuJk0GqiZA+Do4Wxnfae+QJru85Jnx p/cP98Pre9TT2/VqJk36afKZs8EmMj1E0QkkcZrsPHuC+BXUHCzHNLjXg1hKMXqI zLyNDIyifrQ3yvIZQdzBjOf90T046g0jJWlyhTCJ2uGAn84aF++4KypwfYv8gSgf xUNIvb4hvrtTe/3ArneylAP3ZjvIAlqQ2F5d35e9SHTZFu347ab6i8mCLbuo7XMA SisGB7Tblo04dM9eHX0PffLWaiZ1/+2JgUG9c9Or/nC3G6l70G86HQJluc9w== 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=1677593349; x=1677679749; bh=QsMJVdcalhDz2s9tQRNIjHHjuRF5 DTS5XYtiESt55Ug=; b=dTuvBJgFDEe+ZptVC1oDvjPRZkgHzTu26upCKDz56i7U vrpF1nWQyIAn2CrK+7ynYOwGve8VWNAjTlEIelr9msj14sJ4rifXhy4hH2DHQaTD r/Kt8zw59ItmiYxbB80zMjeRk87fxNReUNBwxXy/pwdT9t05u+JN7soWHIcHCalq D6xv8+Pl+Q1ht3aXnLvVqxP3TkMyFb+IO77B7lWgRXvDIjom8yObI2rxNg6Meu8m 4apOeo034c7esRk2qItNXTDChN0IllunneGF5W8YH8I6QG0Yv5IOnXmScRVEANaj XQCJdnMOMNK5UUPWT4zVsuc8Zui1nLMJViJrhQvjbQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudelvddgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 28 Feb 2023 09:09:08 -0500 (EST) Date: Tue, 28 Feb 2023 14:09:06 +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.60 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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: 4PQzkZ5Rfnz4K0l X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 04:27:40PM -0700, Alan Somers wrote: >On Mon, Feb 27, 2023 at 4:11 PM void wrote: >> >> 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? >> -- > >First, check the partition table in the guest. If ZFS is the last >partition, then it isn't hard. The steps are: >* Enlarge the zvol in the host >* Reboot the guest, if it doesn't automatically see the size change. >* Resize the partition in the guest, with a command like "gpart resize >-i 3 vtbd0". You may also need to do "gpart recover vtbd0" >* Then ZFS should automatically resize, if the pool's autoexpand >property is set. If not, do "zpool online -e zroot vtbd0p3". > TYVM thats very helpful. I've saved this also to my dir of sysadmin tips because until now the information wasn't all in one place (well it might be but I couldn't find it at the time) thanks again, --