From owner-freebsd-fs@FreeBSD.ORG Tue Dec 16 17:51:53 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98CCD2A5 for ; Tue, 16 Dec 2014 17:51:53 +0000 (UTC) Received: from webmail2.jnielsen.net (webmail2.jnielsen.net [50.114.224.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 770FC31A for ; Tue, 16 Dec 2014 17:51:52 +0000 (UTC) Received: from [10.10.1.196] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by webmail2.jnielsen.net (8.14.9/8.14.9) with ESMTP id sBGHphF0078341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Dec 2014 10:51:46 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail2.jnielsen.net: Host office.betterlinux.com [199.58.199.60] claimed to be [10.10.1.196] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: Expanding a zpool inside a VM From: John Nielsen In-Reply-To: Date: Tue, 16 Dec 2014 10:51:43 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <90BAD484-1EFD-478F-9A43-60D39242FC1D@jnielsen.net> References: To: javocado X-Mailer: Apple Mail (2.1993) Cc: FreeBSD Filesystems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2014 17:51:53 -0000 On Dec 16, 2014, at 10:44 AM, javocado wrote: > I have a FreeBSD 10.0 installation in a vmware guest and I'd like to = expand > the zpool. Obviously it's very simple to expand the disk size within > vmware, but I just want to make sure this command - which _appears_ to = work > fine - is really safe and sane to properly expand the pool to the full = size > of the the new, larger disk: >=20 > zpool online -e pool /dev/da1 I've been using exactly that command for a long time to extend zpools in = virtual machines with the expected results.