From nobody Sat Sep 17 20:48:58 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 4MVNMs5Y8qz4cQKr for ; Sat, 17 Sep 2022 20:49:13 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: from mail-oo1-xc32.google.com (mail-oo1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 4MVNMr1j8Lz40nG; Sat, 17 Sep 2022 20:49:12 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: by mail-oo1-xc32.google.com with SMTP id t4-20020a4aa3c4000000b00475624f2369so3310142ool.3; Sat, 17 Sep 2022 13:49:12 -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=rHz8neZf3swtSHDswhsLxc8kn2I0tIcsr7r1q8VQKJA=; b=G3ARAGdQ68m77J1TdvSiaQT4uFMnrQJMd5YXFwp6kOckahhKN2s9KwYXGifPmCGNVY ctmBbmJgNAu/d2yFNQGCg/6ZyYMuw4OOsJA0HweOyUlDaK5lPKEnEpZOv8dNwfx2kSIs QQ9vfkVmukK+JfERUSNspcRAgpr150pRbQ+tYq5Lasud052R2nE40lmPbMGcBcwoJy60 FAo0EzHT02rD1X54ro0v5szj9PHl7BVLXwJrxWCFeziBdZNFAdGP+BvoTHRWXktJQ1ln N2rfJ/KdqQyE9555EvFx186SGhF3HnnBMkzVBMjxdNXgVZYS7jQ1W0g5IzdVYwoiAR2r 459A== 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=rHz8neZf3swtSHDswhsLxc8kn2I0tIcsr7r1q8VQKJA=; b=rLYU6ikGjadS846J4c3RMDN+C/2ArZ+i3C+RxVYAv/Ms9rdSqsc3HBScWwP0twemGb 29u4OWlm80EqOiUtNSN081DytmcRk9v9ArwHqHZjfsjv95Um0CXRr2M7Smqs2ovsBEPc EyUAh4UBJVVNw2I/D1R8/UKFoyw8gUHbS7R2ITWJ38EgxWY3Z4oBKnad/UHY5pHWxFfV KroXfeH+Gm9wZOhRRezamaqFZ9AZoYEVfYjG72GUEPgu0j7suqE5tiCORjPf55MyHWyr N9FsNBd5i+hqN8VbiKg4yJIcA+a7HHaDafT4xoKCfZ8hnh+rJUYTLpdcv8uDiIDxcH4V XJxQ== X-Gm-Message-State: ACrzQf3sLDM4c+5o5PxhOZp7s2iX+aV3cidxdkB3S/MyJnZO35MmXBKo CP1vt8BKDe6NBgAADVyGbEu6imr42pwQgvQqcVx28uxSWJSbdw== X-Google-Smtp-Source: AMsMyM5xk0takWJoHh9J33cwgIuRX/UsHB1SyMPTjc2iLXpoW23CXBdlehqmdifZxPxzj2bdnsGOYyR0SDXnRxg8SRM= X-Received: by 2002:a4a:d00f:0:b0:475:6612:c055 with SMTP id h15-20020a4ad00f000000b004756612c055mr4313272oor.25.1663447748988; Sat, 17 Sep 2022 13:49:08 -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:48:58 +0400 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: Alan Somers Cc: freebsd-fs Content-Type: multipart/alternative; boundary="0000000000002e57d205e8e59ca8" X-Rspamd-Queue-Id: 4MVNMr1j8Lz40nG X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=G3ARAGdQ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of milkyindia@gmail.com designates 2607:f8b0:4864:20::c32 as permitted sender) smtp.mailfrom=milkyindia@gmail.com X-Spamd-Result: default: False [-3.92 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.993]; NEURAL_HAM_LONG(-0.98)[-0.984]; NEURAL_HAM_MEDIUM(-0.95)[-0.946]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0: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:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::c32: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 --0000000000002e57d205e8e59ca8 Content-Type: text/plain; charset="UTF-8" On Sun, Sep 18, 2022 at 12:44 AM Alan Somers wrote: > On Sat, Sep 17, 2022 at 2:42 PM milky india wrote: > > > > > > > > On Sun, Sep 18, 2022 at 12:30 AM Alan Somers > wrote: > >> > >> On Sat, Sep 17, 2022 at 2:25 PM milky india > wrote: > >> > > >> > > >> > > >> > On Sun, Sep 18, 2022 at 12:20 AM Alan Somers > wrote: > >> >> > >> >> On Sat, Sep 17, 2022 at 2:03 PM milky india > wrote: > >> >> > > >> >> > > >> >> > > >> >> > On Sat, Sep 17, 2022 at 10:58 PM Alan Somers > 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 > 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 < > asomers@freebsd.org> 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. > >> >> > ---------------------------------------- > >> >> > >> >> Dude, it's easier just to try it, than to ask us. Go for it. The > >> >> worst case scenario if you get the argument wrong is that nothing > >> >> happens. > >> > > >> > > >> > > The worst case scenario if you get the argument wrong is that > nothing happens. > >> > I'm not very sure if I put in the wrong value of s (old size) then > "nothing happens" - I would imagine if I put in a size less than the > current size then possibly the data after that get's lost? Or if I put in a > size greater than the current size then there is a gap in the geli > partition? > >> > I sense some frustration in your reply - but I'm on a live system and > wouldn't want to possibly risk it going kaput at this last step. That's the > reason I'm trying to understand what is the best value of s for geli resize > and how to obtain it. > >> > >> The purpose of the "-s" argument is to tell geli where to find the old > >> label, if the provider isn't already attached. If you supply the > >> wrong argument, then geli won't be able to find the label, and thus > >> won't be able to do anything. It won't destroy any data, and it will > >> always automatically determine the size of the current provider. Of > >> course, if you're worried about losing data, you should always save a > >> copy of /var/backups/ada0p3.eli, as I suggested. > >> -Alan > > > > > > >The purpose of the "-s" argument is to tell geli where to find the old > > > label, if the provider isn't already attached. If you supply the > > > wrong argument, then geli won't be able to find the label, and thus > > > won't be able to do anything. > > > > I think you're confusing the -s argument with something else - the man > page says it's for the old size - that's why I was trying to figure it out > and still haven't been able to quite yet. Although I suspect the > "Mediasize" output for p3 from "geli list" is what the s value should be - > but not very sure : > > > ------------------------------------------------------------------------------------------ > > Additional options include: > > > > -s oldsize The size of the provider before it > was resized. > > > ------------------------------------------------------------------------------------------------ > > Yes, that's right. geli needs to know the old size of the provider in > order to find the provider's old label. > Thanks for acknowledging. I tried to do this using the s value from geli list - it won't let me even do it as sudo : Getting a bit scared now. Should I not be writing `.eli` part? ----------------------------------------------------------------- sudo geli resize -s 311481593856 /dev/ada0p3.eli Password: geli: Cannot open /dev/ada0p3.eli: Operation not permitted. sudo geli resize -s 311481593856 ada0p3.eli geli: Cannot open ada0p3.eli: Operation not permitted. --------------------------------------------------------------------------- --0000000000002e57d205e8e59ca8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Sep 18, 2022 at 12:44 AM Alan= Somers <asomers@freebsd.org&= gt; wrote:
On Sa= t, Sep 17, 2022 at 2:42 PM milky india <milkyindia@gmail.com> wrote:
>
>
>
> On Sun, Sep 18, 2022 at 12:30 AM Alan Somers <asomers@freebsd.org> wrote:
>>
>> On Sat, Sep 17, 2022 at 2:25 PM milky india <milkyindia@gmail.com> wrote:=
>> >
>> >
>> >
>> > On Sun, Sep 18, 2022 at 12:20 AM Alan Somers <asomers@freebsd.org> wr= ote:
>> >>
>> >> On Sat, Sep 17, 2022 at 2:03 PM milky india <milkyindia@gmail.com= > wrote:
>> >> >
>> >> >
>> >> >
>> >> > 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 Somer= s <asomers@free= bsd.org> wrote:
>> >> >> >>
>> >> >> >> On Sat, Sep 17, 2022 at 12:31 PM milky = india <milkyin= dia@gmail.com> 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 gel= i man page. I was specifically warned against using "geli resize"= since it may not work as expected https://forums.FreeBSD.org/threa= ds/how-to-extend-zfs-geli-encrypted-disk-space-not-showing.86447/post-58164= 2
>> >> >> >> > Is this advise wrong?
>> >> >> >> > > "The geli has autoresize= flag which will handle the new provider size after gpart resize command.&q= uot;
>> >> >> >> > 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 A= lan Somers <aso= mers@freebsd.org> wrote:
>> >> >> >>
>> >> >> >> top-posting is where you insert your re= ply above the previous email.
>> >> >> >> Bottom posting is where you insert your= reply below it, like I'm
>> >> >> >> doing.=C2=A0 The forum user said that y= ou shouldn't need to run "geli
>> >> >> >> resize" because the AUTORESIZE fla= g is on.=C2=A0 But as you can see from
>> >> >> >> your "geli list" output, it&#= 39;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/ada= 0p3.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 ar= e concerned about) - hence the advice given to not use "geli resize&qu= ot; isn't applicable here. Am I understanding this correctly?
>> >> >>
>> >> >> Yes
>> >> >>
>> >> >> >
>> >> >> > > So you need to run "geli resize&q= uot;
>> >> >> > Is this the only command that I need to run= to resize my geli partition?
>> >> >>
>> >> >> Yes
>> >> >>
>> >> >> >
>> >> >> > > The "-s" flag should be unne= cessary since your provider is
>> >> >> > already online.
>> >> >> > Ok thanks.
>> >> >> >
>> >> >> > >You might want to make a copy of /var/b= ackups/ada0p3.eli, just in case you make a mistake.
>> >> >> > Don't have the luxury of backup current= ly.
>> >> >>
>> >> >> 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" would reflect the size to be 458G? (vs 290G current= ly)
>> >> >> > And that's the output I can trust to ha= ve solved the issue - or is there more to it?
>> >> >>
>> >> >> Yes.
>> >> >
>> >> > > The "-s" flag should be unnecessary s= ince your provider is already online.
>> >> > When I try to run "geli resize /dev/ada0p3.eli&= quot; it complains. So I guess options s is must ? If yes - do I need to pu= t in the exact size down to bytes from the output of geli list ? Under &quo= t;Mediasize" ?
>> >> > ---------------------------------------
>> >> > geli: Option 's' not specified.
>> >> > ----------------------------------------
>> >>
>> >> Dude, it's easier just to try it, than to ask us.=C2= =A0 Go for it.=C2=A0 The
>> >> worst case scenario if you get the argument wrong is that= nothing
>> >> happens.
>> >
>> >
>> > > The worst case scenario if you get the argument wrong is= that nothing happens.
>> > I'm not very sure if I put in the wrong value of s (old s= ize) then "nothing happens" - I would imagine if I put in a size = less than the current size then possibly the data after that get's lost= ? Or if I put in a size greater than the current size then there is a gap i= n the geli partition?
>> > I sense some frustration in your reply - but I'm on a liv= e system and wouldn't want to possibly risk it going kaput at this last= step. That's the reason I'm trying to understand what is the best = value of s for geli resize and how to obtain it.
>>
>> The purpose of the "-s" argument is to tell geli where t= o find the old
>> label, if the provider isn't already attached.=C2=A0 If you su= pply the
>> wrong argument, then geli won't be able to find the label, and= thus
>> won't be able to do anything.=C2=A0 It won't destroy any d= ata, and it will
>> always automatically determine the size of the current provider.= =C2=A0 Of
>> course, if you're worried about losing data, you should always= save a
>> copy of /var/backups/ada0p3.eli, as I suggested.
>> -Alan
>
>
>=C2=A0 >The purpose of the "-s" argument is to tell geli w= here to find the old
> > label, if the provider isn't already attached.=C2=A0 If you s= upply the
> > wrong argument, then geli won't be able to find the label, an= d thus
> > won't be able to do anything.
>
> I think you're confusing the -s argument with something else - the= man page says it's for the old size - that's why I was trying to f= igure it out and still haven't been able to quite yet. Although I suspe= ct the "Mediasize" output for p3 from "geli list" is wh= at the s value should be - but not very sure :
> ----------------------------------------------------------------------= --------------------
> Additional options include:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0-s oldsize=C2=A0 =C2=A0 =C2=A0 =C2=A0 The size of the provider before= it was resized.
> ----------------------------------------------------------------------= --------------------------

Yes, that's right.=C2=A0 geli needs to know the old size of the provide= r in
order to find the provider's old label.

=
Thanks for acknowledging. I tried to do this using the s value from ge= li list - it won't let me even do it as sudo :
Getting a bit = scared now. Should I not be writing `.eli` part?=C2=A0
-----------------= ------------------------------------------------
sudo geli resize -s 311= 481593856 /dev/ada0p3.eli
Password:
geli: Cannot open /dev/ada0p3.el= i: Operation not permitted.
sudo geli resize -s 311481593856 ada0p3.el= i
geli: Cannot open ada0p3.eli: Operation not permitted.
--------------------------------------------------------------------------= -=C2=A0
--0000000000002e57d205e8e59ca8--