From nobody Mon Feb 27 23:27:40 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 4PQc9k3V48z3tK5w for ; Mon, 27 Feb 2023 23:27:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f44.google.com (mail-vs1-f44.google.com [209.85.217.44]) (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 4PQc9j38D8z3wdB for ; Mon, 27 Feb 2023 23:27:53 +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.44 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=none Received: by mail-vs1-f44.google.com with SMTP id d7so14047643vsj.2 for ; Mon, 27 Feb 2023 15:27:53 -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=trobtplCUCgSKaDxL8oB/+7wLOiBLA/qXp1xPK/VbYg=; b=CFlci+/iLoQ6Cal5jXSCZAqk9Xd1Iz+y4bzHD9vu18VihKDEomn1a7uueMc0i11jYN lI6DwGYwAkFnI2NVI9YKBdvXOcIggXpHXVvw4vmb4d2GqiG1GQuqQ2HWEl4imBOKG2O4 Uiirxx1p/QV1IQ6Sz1PqLwifFez7vQEWJncKUMQPam1+YscEqvQFse+CX66OngaHvzwA kqm8p2mrGr+nhz/BqfySrwF9rSyk4h90pejCLYjg7ePpVUz6GH6Ac46V9QovTxf7flj7 MIpFsdinTaHxWI7D82OVxDsZXwiy7ArIEmb+eBTBqQOQiZMbdoxKKyJi84uIh8ddy4Dn AYQQ== X-Gm-Message-State: AO0yUKXA5UiM/12ux8GDKvNpEJqsR3lkMj9fiHsx0NW/kJy+bQ2c5iaQ jGC5Sxf7Q34+qlEark6z6UA7CDtDD7BXs2wVXGA160ZCAeM= X-Google-Smtp-Source: AK7set9kyevO/kbcKUV7HBPmV3VH2qyjqmmaLfr4iJbJoE6qkpfK2q0h24tbLaF4QyjuljZ5ipF2cwDBCWTXs1fDAgc= X-Received: by 2002:ab0:5b59:0:b0:68b:9eed:1c7d with SMTP id v25-20020ab05b59000000b0068b9eed1c7dmr456000uae.0.1677540472201; Mon, 27 Feb 2023 15:27:52 -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 16:27:40 -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 [-2.92 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.915]; 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.44:from]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.44: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: 4PQc9j38D8z3wdB X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N 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".