From owner-freebsd-fs@freebsd.org Sun Sep 13 13:03:53 2020 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 522783D9A9F for ; Sun, 13 Sep 2020 13:03:53 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 4Bq8nh4CYgz49sF for ; Sun, 13 Sep 2020 13:03:52 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 1D5384CE for ; Sun, 13 Sep 2020 09:03:51 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 13 Sep 2020 09:03:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=dysVl5YHN3HOSrbQ8Ikc84TsSbm 2lWDEvoHOip1CwPo=; b=Cli9P/ELkJ7Z4gwkPh1sjXU5XBXDHKGfKrCK9dm4B7a eX4YCkPK9Do6HKZw/PS89oNeVBFQnLZKIlIjcsfX/pOleO5RQogcFlTJqPxKx54S 9f/8ROJwtJpbU6rl6lTFO2WdrDolkvjbT3laP1xozU2AOvEdjJSKonhbpx4XCo1a psQdWlqOFO+2qYuv510+bUef5jggLxS7pajFiuWgg3kLOuJi8vc0kGnIqtV7fFOS RUkNAkGrnrO6VpyTyIziSmGCtYlGVqjlgcU/idznBZidkx4qZ89S1iZLNOHBbgXY +DP670LFuTcy6KBvJ/OaYmxXHmN6mlMFttrNaU3sN6g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=dysVl5 YHN3HOSrbQ8Ikc84TsSbm2lWDEvoHOip1CwPo=; b=peBTBIAkrTXJq1oWtHIwWx 3vMQGwMIlFxrnR32/1XmFHYuZuKLSEQ2r2nUpz2zY5vlOGPE7W82dh3v5evuf/mz AInqsj5psFREcsZKX3Ltnp/OU5d2y1ri/F4R5eguK5ddIpAue9a0O+w/xNb2FO/U pjysiVp5DRgHd7llijMHX10H776XZocavn6laHJugNXb3AUdOF1cfxzgy/xvg13z l40fTW6Vg6AVfUzixrP2JVNBuqByFMv/IFegL6lYqyjrNxVt271NW0gqzp9H/fEL Hb3bWL/H0vb7KCHDTmrM15OPm7d9htHQiZf3g+PjO7PhFsDpN9Hz10UhDSyr0JmQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudeifedgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucfkphepkedvrdejtddrledurdelleen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthh dqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: from bastion.zyxst.net (bastion.zyxst.net [82.70.91.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 01148306467D for ; Sun, 13 Sep 2020 09:03:49 -0400 (EDT) Date: Sun, 13 Sep 2020 14:03:21 +0100 From: tech-lists To: freebsd-fs@freebsd.org Subject: Re: how to resize a zvol (legacy version of zfs) Message-ID: <20200913130321.GJ91422@bastion.zyxst.net> Mail-Followup-To: freebsd-fs@freebsd.org References: <20200913121522.GI91422@bastion.zyxst.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="huG+SbfbdD6eblZQ" Content-Disposition: inline In-Reply-To: <20200913121522.GI91422@bastion.zyxst.net> X-Rspamd-Queue-Id: 4Bq8nh4CYgz49sF X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm3 header.b=Cli9P/EL; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=peBTBIAk; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 64.147.123.20 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-5.89 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm3,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.05)[-1.046]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[64.147.123.20:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,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)[-0.996]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zyxst.net]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.15)[-1.150]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MAILMAN_DEST(0.00)[freebsd-fs]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2020 13:03:53 -0000 --huG+SbfbdD6eblZQ Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 13, 2020 at 01:14:55PM +0100, tech-lists wrote: >Hi, > >I have a bhyve instance mounted on a zvol on a freebsd-12-stable host. I'm= not >using any special tool to manage the bhyve apart from screen. > >How can I resize the bhyve instance wihtout making it unusable? The zol is >64GB and I'd like to make it 256GB. As a test, I've successfully resized it on the host. The problem is when the guest boots up, the guesnt's growfs (the fs in the guest is ufs) cant see t= he space. On the guest I did this: # sysrc growfs_enable=3DYES growfs_enable: NO -> YES # reboot then on the host, did this: # zfs get volsize data/current NAME PROPERTY VALUE SOURCE data/current volsize 64G local # zfs set volsize=3D256G data/current # zfs get volsize data/current NAME PROPERTY VALUE SOURCE data/current volsize 256G local log into the guest... # mount=20 /dev/vtbd0s1a on / (ufs, local, journaled soft-updates) devfs on /dev (devfs) # growfs / growfs: requested size 61GB is not larger than the current filesystem size 61GB # gpart recover /dev/vtbd0 vtbd0 recovering is not needed # gpart resize -i 1 /dev/vtbd0 GEOM_PART: vtbd0s1 was automatically resized. Use `gpart commit vtbd0s1` to save changes or `gpart undo vtbd0s1` to re= vert them. vtbd0s1 resized Sep 13 13:36:31 current syslogd: last message repeated 1 times # gpart commit vtbd0s1 #=20 # growfs / growfs: requested size 61GB is not larger than the current filesystem size 61GB What am I doing wrong? --=20 J. --huG+SbfbdD6eblZQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl9eGKoACgkQs8o7QhFz NAX5IRAAqLkZE2Y8qgvRV6K2CENoXQYoArQNtWZGnLkpRO2H+qZhnxcvpJsEHvTH 67+97O2DgoqDw0XeBBy7V2aIZiMUvZ/WaDuoMXUWs9INuGPiKTdnz2arCbSVNQ03 rf0H4ugC4iOKs17BpLJrLAQyqVcBNs9ao+puq6ouODFh2hHlekvN3Gk6jhTPNfW6 KdDSqVVLk3iOmLHsCCYhwo/Tmfwlpn71jYmDqAMkKupyve6BCBmJ/62GOorpZcJS zoH9OxBv70A06g3y1PhHzundSDPQfvjshWRPv3qSlll6p0x20g+LE8l8CS1UMKmv 2pOGJkF6R9dOsIYMKeO8yUOXZ1tW6xrEs3bPa1nacVYtUaBK39mDZ/D5Nm1swIA5 8cMtcjxPu5acqTxHlEg7n+mwx/d7Taw90GTq6o/HJk7q452cTV3KOrlxSbTr2VfV EwRwbJg0qEX3FmvT+dq88uUClGd800fMOSiyIj5pd4dtLLO1dDB2B/srAr90qTEf 0AFDFhU1xzexlAqJCuRSkp0aniRyY4f0/AOqdaDbi5wneLjdBdg01BTHeKQCAzph DFiPS8FEBPtEOiYGwNNXmwvYdbP8d4Jmn1IhijxzNbVTWSeWdh+pqca5onSFZR+V oqwsXL9KBEiqdtceLQUCLw17McZUALj8azQZJrSncqacwr/EBZE= =TXX+ -----END PGP SIGNATURE----- --huG+SbfbdD6eblZQ--