From nobody Sat Sep 17 18:31:14 2022 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 4MVKJs0Zm4z4c1Fj for ; Sat, 17 Sep 2022 18:31:25 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (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 4MVKJr4lWbz3jDJ; Sat, 17 Sep 2022 18:31:24 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-11eab59db71so56542337fac.11; Sat, 17 Sep 2022 11:31:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=ZlyIM7kzRyK9HAR25IRO+V3w9pfLSV2dJ7StlDjRlkg=; b=m8zq2z9JWfYhk9mtYeswOR+r1uM9dARVusF2R1sbgFTPrHhm0R+QoaEU9bcVLrwlbp A/+vffmEzZEb/dVBsaWxO8qL/dVlarIT36i8FTXL3jPT128zjubDRQOhGUGG8RBqv1uS 9wsvmc2k5w1YPEkW8uKRFq+sVlVbCrry5xjFsAk9E0L+EI0E4XTgwCEqwuGm/wYhBW1y k8FFdpNMX2TRTnTmj1+LdSoPaoPiLVt307yv/QMTKVpx1Ycxp5UPlhr+39aP0Nrs304T URGLUL1UYB8Gjs9S8sEfVWCGpA7O4FavrIglYQpGgkwSBeYoZ8oQdS3K6oxo+3rQhTjE XVuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=ZlyIM7kzRyK9HAR25IRO+V3w9pfLSV2dJ7StlDjRlkg=; b=EOgDJRSt3NEouRLUFFAenYqDi8otHkEAQkxanosdontVHFLE7M6/DzwT7IuZQ5dgcp ipK+NNuK9B5Jzs+JkAIPAUXXpQR8OG1k6z9waCxo3CyQVJaTdMkUab/9LGsLx9FjkPPd pQ8hXf58BT/899tNtU8SeU1KwmAKcTFj35co2fUhEHXMY5sLdivltm2nJ47adQ4bBd6L 6uHEiivpBzFWeTagUKPphxcXgVb/5EsE8TIfjVBnELMGNTKQ5yYIwLGolTi2eBsZWAtv VFlhwq4DIR3CWD2IAXDMjOQYikLhsC0lfLK7Rpqzo+US8HEP/McOer5+HEajSgYhmSF6 8LAw== X-Gm-Message-State: ACgBeo15iaeDtenS6XPWlO6A+gSLJQ4XiUz99VrJL6cwjY0SptHzi4xX 8Zwy8e39DwMj8cuSGEnk9MvzRlvll+qyjpZtxo8Zi+6GdbhuGQ== X-Google-Smtp-Source: AA6agR4dsfy4dSACtTfta4XMo+q8DKz56dPGqUwqMoiL2RFZaCgXSt8s1bG9ZKhItmx4CbYsZ4CwTkh+0Z/ucjOczL8= X-Received: by 2002:a05:6871:b2a:b0:12b:91ce:e45b with SMTP id fq42-20020a0568710b2a00b0012b91cee45bmr11606831oab.291.1663439483756; Sat, 17 Sep 2022 11:31:23 -0700 (PDT) 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: milky india Date: Sat, 17 Sep 2022 22:31:14 +0400 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: Alan Somers Cc: freebsd-fs Content-Type: multipart/alternative; boundary="00000000000088e49105e8e3afd5" X-Rspamd-Queue-Id: 4MVKJr4lWbz3jDJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=m8zq2z9J; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of milkyindia@gmail.com designates 2001:4860:4864:20::2c as permitted sender) smtp.mailfrom=milkyindia@gmail.com X-Spamd-Result: default: False [-3.74 / 15.00]; NEURAL_HAM_LONG(-0.95)[-0.948]; NEURAL_HAM_MEDIUM(-0.90)[-0.897]; NEURAL_HAM_SHORT(-0.89)[-0.892]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::2c:from]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N --00000000000088e49105e8e3afd5 Content-Type: text/plain; charset="UTF-8" Sorry about that, again - I'm not sure what you mean by bottom-post vs top-post. Be that as it may - I read the geli man page. I was specifically warned against using "geli resize" since it may not work as expected https://forums.FreeBSD.org/threads/how-to-extend-zfs-geli-encrypted-disk-space-not-showing.86447/post-581642 Is this advise wrong? > "The geli has autoresize flag which will handle the new provider size after gpart resize command." followed by > You are right, no geli resize needed. What would be the correct sequence of commands to fix this - Simply "geli resize" ? (the -s option seems to be additional, will it figure it out without providing s?) On Sat, Sep 17, 2022 at 10:20 PM Alan Somers wrote: > On Sat, Sep 17, 2022 at 12:07 PM milky india wrote: > > > > Apologies about that - output of "geli list" below : > > Seems like the provider is showing the old value (290G) while the > consumer is showing the resized value (458G) - so now I'm confused about > what is to be done and how to resolve this (not very familiar and still > learning) > > > > ---------------------------------------------------------------------- > > geli list > > Geom name: ada0p3.eli > > State: ACTIVE > > EncryptionAlgorithm: AES-XTS > > KeyLength: 256 > > Crypto: accelerated software > > Version: 7 > > UsedKey: 0 > > Flags: BOOT, GELIBOOT > > KeysAllocated: 73 > > KeysTotal: 73 > > Providers: > > 1. Name: ada0p3.eli > > Mediasize: 311481593856 (290G) > > Sectorsize: 4096 > > Mode: r1w1e1 > > Consumers: > > 1. Name: ada0p3 > > Mediasize: 491516858368 (458G) > > Sectorsize: 512 > > Stripesize: 0 > > Stripeoffset: 8590983168 > > Mode: r1w1e1 > > > > Geom name: ada0p2.eli > > State: ACTIVE > > EncryptionAlgorithm: AES-XTS > > KeyLength: 128 > > Crypto: accelerated software > > Version: 7 > > Flags: ONETIME, W-DETACH, W-OPEN, AUTORESIZE > > KeysAllocated: 2 > > KeysTotal: 2 > > Providers: > > 1. Name: ada0p2.eli > > Mediasize: 8589934592 (8.0G) > > Sectorsize: 4096 > > Mode: r1w1e0 > > Consumers: > > 1. Name: ada0p2 > > Mediasize: 8589934592 (8.0G) > > Sectorsize: 512 > > Stripesize: 0 > > Stripeoffset: 1048576 > > Mode: r1w1e1 > > > ---------------------------------------------------------------------------------------- > > So yes, you need to resize the geli device. Read the geli man page > for details. Also, when you reply please bottom-post rather than > top-post. It makes the mail archives more readable. > -Alan > --00000000000088e49105e8e3afd5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry about that, again - I'm not sure what you mean b= y bottom-post vs top-post.

Be that as it may - I read th= e geli man page. I was specifically warned against using "geli resize&= quot; since it may not work as expected=C2=A0https://forums.FreeBSD.org/threads/how-to-extend-zfs-geli-e= ncrypted-disk-space-not-showing.86447/post-581642=C2=A0
Is th= is advise wrong?=C2=A0
> "The geli has a= utoresize flag which will handle the new provider size after gpart resize c= ommand."=C2=A0
followed by
>=C2=A0You are right, no=C2=A0geli resize=C2=A0needed.

What would be the correct sequence of commands to fix this - Simply &quo= t;geli resize" ? (the -s option seems to be additional, will it figure= it out without providing s?)

On Sat, Sep 17, 2022 at 10:20 PM Alan So= mers <asomers@freebsd.org>= wrote:
On Sat, = Sep 17, 2022 at 12:07 PM milky india <milkyindia@gmail.com> wrote:
>
> Apologies about that - output of "geli list" below :
> Seems like the provider is showing the old value (290G) while the cons= umer is showing the resized value (458G) - so now I'm confused about wh= at is to be done and how to resolve this (not very familiar and still learn= ing)
>
> ----------------------------------------------------------------------=
> geli list
> Geom name: ada0p3.eli
> State: ACTIVE
> EncryptionAlgorithm: AES-XTS
> KeyLength: 256
> Crypto: accelerated software
> Version: 7
> UsedKey: 0
> Flags: BOOT, GELIBOOT
> KeysAllocated: 73
> KeysTotal: 73
> Providers:
> 1. Name: ada0p3.eli
>=C2=A0 =C2=A0 Mediasize: 311481593856 (290G)
>=C2=A0 =C2=A0 Sectorsize: 4096
>=C2=A0 =C2=A0 Mode: r1w1e1
> Consumers:
> 1. Name: ada0p3
>=C2=A0 =C2=A0 Mediasize: 491516858368 (458G)
>=C2=A0 =C2=A0 Sectorsize: 512
>=C2=A0 =C2=A0 Stripesize: 0
>=C2=A0 =C2=A0 Stripeoffset: 8590983168
>=C2=A0 =C2=A0 Mode: r1w1e1
>
> Geom name: ada0p2.eli
> State: ACTIVE
> EncryptionAlgorithm: AES-XTS
> KeyLength: 128
> Crypto: accelerated software
> Version: 7
> Flags: ONETIME, W-DETACH, W-OPEN, AUTORESIZE
> KeysAllocated: 2
> KeysTotal: 2
> Providers:
> 1. Name: ada0p2.eli
>=C2=A0 =C2=A0 Mediasize: 8589934592 (8.0G)
>=C2=A0 =C2=A0 Sectorsize: 4096
>=C2=A0 =C2=A0 Mode: r1w1e0
> Consumers:
> 1. Name: ada0p2
>=C2=A0 =C2=A0 Mediasize: 8589934592 (8.0G)
>=C2=A0 =C2=A0 Sectorsize: 512
>=C2=A0 =C2=A0 Stripesize: 0
>=C2=A0 =C2=A0 Stripeoffset: 1048576
>=C2=A0 =C2=A0 Mode: r1w1e1
> ----------------------------------------------------------------------= ------------------

So yes, you need to resize the geli device.=C2=A0 Read the geli man page for details.=C2=A0 Also, when you reply please bottom-post rather than
top-post.=C2=A0 It makes the mail archives more readable.
-Alan
--00000000000088e49105e8e3afd5--