From nobody Sat Sep 17 20:03:15 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 4MVMM4530Lz4cHMw for ; Sat, 17 Sep 2022 20:03:28 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 4MVMM3739dz3t75; Sat, 17 Sep 2022 20:03:27 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: by mail-oi1-x22b.google.com with SMTP id w125so10096430oig.3; Sat, 17 Sep 2022 13:03:27 -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=gG+zzCbniDj991dD5pOHWyGN6JRj4ICABSF6OGj10rI=; b=OlJTAwXDyagHpyRGb3wN5LD6soAoJgtDtslv/Vt/r43XCjiKsXxPkLgg0NAKsmw7+k DQTe0gnYj37M/9XaytK34YrqBIZAIe6VeKmc7RLO/itiZtds4pWffsY8uQ/8iAix6aSz FL4GhdU0qbWRSsRdxjdDFx7jFo1S99RCe022c9Bhe6jpejlJXR9zOnubPr9P32GpzyQG bcaBoX6C2qlDXcrUEU3Udnk8mFGP5of+VyYcQD/zWjnbnXj637hyGIDl+85htXMYMxIP h5ABYzP5CtrIYUxbblDZLT1/vMhYSJ8B2rlzECbG9wUvuNffLRIsuMSyzK3H75K6TNNS T8rQ== 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=gG+zzCbniDj991dD5pOHWyGN6JRj4ICABSF6OGj10rI=; b=nJ4/89MjxQSg/gUnCbzXs2CkhjG5u2yaGkFYRC3EFhH7seB0TfacC0Htq5BlLEi/b/ RLjd9yO/ex736zEwzKLpUdtvuGLOEL83alRZpZ9VcdxLhIlbKN52BuTitEeg4LsAeIIB rmeHRT2AjZRU5dZ2sd0FVLpGypdesXehC1PgSULQb+NF1uJJ8eMYnRJ6tquKi52x8kDW xix8XoKKj3yWbuYquw28jTLASN69EAS6v6sGtpf6himu4z09S4MgfQDWHuKnu4YU1kqW ln7ntSbtWcO9djwnaQlz+C9L9LnjM4tz9R79jyvYHyRsnWKQvVNlhf8C0Z7NZWEzXoUz ISwQ== X-Gm-Message-State: ACgBeo0Txfdot7qFH8JmSwHQVP++LmdE5jAwFh8oFNJAqpcanhsucJJh QHG/Qe1AS8Y94J231sX2roB5CNbBhzRp1HjzOQdoXTUFA+nGDA== X-Google-Smtp-Source: AA6agR7OpVpgOq21O7Fu0L3j4uNR5ludM5hAbiYVX3abnA9Rs4wYkR8yZtVKpufS9/v+Ssi6yzFGQxLT/P7Ctx1PGek= X-Received: by 2002:aca:ab44:0:b0:34f:6f58:43f6 with SMTP id u65-20020acaab44000000b0034f6f5843f6mr9036713oie.98.1663445006022; Sat, 17 Sep 2022 13:03:26 -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: Sun, 18 Sep 2022 00:03:15 +0400 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: Alan Somers Cc: freebsd-fs Content-Type: multipart/alternative; boundary="000000000000affec105e8e4f81b" X-Rspamd-Queue-Id: 4MVMM3739dz3t75 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=OlJTAwXD; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of milkyindia@gmail.com designates 2607:f8b0:4864:20::22b as permitted sender) smtp.mailfrom=milkyindia@gmail.com X-Spamd-Result: default: False [-3.84 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.94)[-0.945]; NEURAL_HAM_LONG(-0.89)[-0.893]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::22b:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N --000000000000affec105e8e4f81b Content-Type: text/plain; charset="UTF-8" On Sat, Sep 17, 2022 at 10:58 PM Alan Somers wrote: > On Sat, Sep 17, 2022 at 12:52 PM milky india wrote: > > > > > > > > On Sat, Sep 17, 2022 at 10:43 PM Alan Somers > wrote: > >> > >> On Sat, Sep 17, 2022 at 12:31 PM milky india > wrote: > >> > > >> > 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: > >> > >> top-posting is where you insert your reply above the previous email. > >> Bottom posting is where you insert your reply below it, like I'm > >> doing. The forum user said that you shouldn't need to run "geli > >> resize" because the AUTORESIZE flag is on. But as you can see from > >> your "geli list" output, it's actually off. So you need to run "geli > >> resize". The "-s" flag should be unnecessary since your provider is > >> already online. At any rate, you can try it both ways. You might > >> want to make a copy of /var/backups/ada0p3.eli, just in case you make > >> a mistake. > > > > Thanks - I hope I am bottom posting this as was expected of me. > > > > So if I understand correctly the AUTORESIZE flag is present for adaop2 > and NOT for adap3 (which is the partition we are concerned about) - hence > the advice given to not use "geli resize" isn't applicable here. Am I > understanding this correctly? > > Yes > > > > > > So you need to run "geli resize" > > Is this the only command that I need to run to resize my geli partition? > > Yes > > > > > > The "-s" flag should be unnecessary since your provider is > > already online. > > Ok thanks. > > > > >You might want to make a copy of /var/backups/ada0p3.eli, just in case > you make a mistake. > > Don't have the luxury of backup currently. > > Um, ok. I can't guess why you aren't able to do that, but it isn't > strictly necessary. > > > > > I suppose at the end of it - if this works - "geli list" would reflect > the size to be 458G? (vs 290G currently) > > And that's the output I can trust to have solved the issue - or is there > more to it? > > Yes. > > The "-s" flag should be unnecessary since your provider is already online. When I try to run "geli resize /dev/ada0p3.eli" it complains. So I guess options s is must ? If yes - do I need to put in the exact size down to bytes from the output of geli list ? Under "Mediasize" ? --------------------------------------- geli: Option 's' not specified. ---------------------------------------- --000000000000affec105e8e4f81b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=C2=A0=

On Sat, Sep 17, 2022 at 10:58 PM Alan Somers <asomers@freebsd.org> wrote:
On Sat, Sep 17, 2022 at 12:52 PM= milky india <= milkyindia@gmail.com> wrote:
>
>
>
> On Sat, Sep 17, 2022 at 10:43 PM Alan Somers <asomers@freebsd.org> wrote:
>>
>> On Sat, Sep 17, 2022 at 12:31 PM milky india <milkyindia@gmail.com> wrote= :
>> >
>> > Sorry about that, again - I'm not sure what you mean by b= ottom-post vs top-post.
>> >
>> > Be that as it may - I read the geli man page. I was specifica= lly warned against using "geli resize" since it may not work as e= xpected https://forums.FreeBSD.org/threads/how-to-extend-zfs-geli-e= ncrypted-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, wil= l it figure it out without providing s?)
>> >
>> > On Sat, Sep 17, 2022 at 10:20 PM Alan Somers <asomers@freebsd.org> wr= ote:
>>
>> top-posting is where you insert your reply above the previous emai= l.
>> Bottom posting is where you insert your reply below it, like I'= ;m
>> doing.=C2=A0 The forum user said that you shouldn't need to ru= n "geli
>> resize" because the AUTORESIZE flag is on.=C2=A0 But as you c= an see from
>> your "geli list" output, it's actually off.=C2=A0 So= you need to run "geli
>> resize".=C2=A0 The "-s" flag should be unnecessary = since your provider is
>> already online.=C2=A0 At any rate, you can try it both ways.=C2=A0= You might
>> want to make a copy of /var/backups/ada0p3.eli, just in case you m= ake
>> a mistake.
>
> Thanks - I hope I am bottom posting this as was expected of me.
>
> So if I understand correctly the AUTORESIZE flag is present for adaop2= and NOT for adap3 (which is the partition we are concerned about) - hence = the advice given to not use "geli resize" isn't applicable he= re. Am I understanding this correctly?

Yes

>
> > So you need to run "geli resize"
> Is this the only command that I need to run to resize my geli partitio= n?

Yes

>
> > The "-s" flag should be unnecessary since your provider= is
> already online.
> Ok thanks.
>
> >You might want to make a copy of /var/backups/ada0p3.eli, just in = case you make a mistake.
> Don't have the luxury of backup currently.

Um, ok.=C2=A0 I can't guess why you aren't able to do that, but it = isn't
strictly necessary.

>
> I suppose at the end of it - if this works - "geli list" wou= ld reflect the size to be 458G? (vs 290G currently)
> And that's the output I can trust to have solved the issue - or is= there more to it?

Yes.
> The "-s&q= uot; flag should be unnecessary since your provider is=C2=A0already online.
When I try to run "geli resize /dev/ada0p3.eli&qu= ot; it complains. So I guess options s is must ? If yes - do I need to put = in the exact size down to bytes from the output of geli list ? Under "= Mediasize" ?
---------------------------------------
geli: Option 's' not specified.
------------------= ----------------------=C2=A0
--000000000000affec105e8e4f81b--