From nobody Mon Feb 27 22:52:46 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 4PQbPS2NZyz3tGXM for ; Mon, 27 Feb 2023 22:53:00 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f42.google.com (mail-vs1-f42.google.com [209.85.217.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PQbPR0y6Cz3rcL for ; Mon, 27 Feb 2023 22:52:59 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.217.42 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=none Received: by mail-vs1-f42.google.com with SMTP id o2so13838272vss.8 for ; Mon, 27 Feb 2023 14:52:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YI077fByBLsxmMh9PDwummKDKdoTfRA5S/djKFBRmvs=; b=NQH15ivDuehBgTnzb9F6y3SSrXvSj4MDjaJcgwgev11+OLb4N447nySfQsYXBuIYO8 vkL/n/z+9WP0tREIhgick02eC2HzDPZx5Bvd/L/mSfDNCVCcyuGW5vicE7U5GUyXETun f929ZKMtApWnSgCJHzloYo9zGehNk9aCvAgy3LhMQhSMTb3FYD9UyuBTle0hC7zTnQ/j H2Qg1oAD2FlCSRbrjsdI1HyBDz+YRRbg2cU44IB+As7W9LAombZ6SaF6vtsQWKOKcIlk fDTKgQvAaQP6L5zGQ9AiQ634U3c+8hPoEhEoh+pJfJNHBe8DVShDOxcygGNFJHw3Al4Y Lp3Q== X-Gm-Message-State: AO0yUKUj8ZMCvhCJmv/oO0vfDu8cf0128Nm+pAfzWUgxtR9VUdwzbol4 JD3YYsMTILkpp3dVIydgsIoaRI4dMnTVk91JqQjeUgaN X-Google-Smtp-Source: AK7set8y3/QX39RxAHLYhRYq1x2R9JgrJ+VBYXn6HNPSlXfU1ecrSiAGxoRlZHiEdJipkm/civHIS1NcgVKLiYzo6oE= X-Received: by 2002:a05:6122:18a4:b0:401:1c83:fba3 with SMTP id bi36-20020a05612218a400b004011c83fba3mr115049vkb.3.1677538377705; Mon, 27 Feb 2023 14:52:57 -0800 (PST) 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 References: In-Reply-To: From: Alan Somers Date: Mon, 27 Feb 2023 15:52:46 -0700 Message-ID: Subject: Re: can another disk be added to a zfs stripe To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_NA(0.00)[freebsd.org]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.42:from]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.42:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[asomers]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4PQbPR0y6Cz3rcL X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 11:05 AM void wrote: > > 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, > -- 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.