From nobody Sat Sep 17 21:20:40 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 4MVP4N2DRSz4cVsZ for ; Sat, 17 Sep 2022 21:20:52 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 4MVP4M4lHQz43v0; Sat, 17 Sep 2022 21:20:51 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: by mail-ot1-x334.google.com with SMTP id x23-20020a056830409700b00655c6dace73so14996948ott.11; Sat, 17 Sep 2022 14:20:51 -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=cgTVUOJGo+c7C8aMlfD02vIq4b+WHb0noQ/YYuerNfY=; b=Ts1OceD0VBRABVTVc0nHeBFl41LHx7c3ivl4otYzpHz0odQhyRqjq/KUYag36AU123 kxPX4OWSQ5XwEd2QJxgclWgg+jLRYfIH6FICKlMPgi82ADE5xQT5gLbnzoxzmzSFFewL h0lG+zesByMhaMSjtiiOtnVKYbRrlKEMd3JU1ZwErSzzRV96WgKebvx2BwCRBbzIUzfR bgUrTFVjrUA8nJtN+nxS1aTaBm07sKOsC/5slNozeF+dNm2rWSOIg7v7DcE0AET+DtAt HE9RpVHetdQ7/l3tIoKlCVXfsGp5vZKuprXCvask6uhKEFQdwNoq2Mh8jEM0TGuS34X3 +Bag== 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=cgTVUOJGo+c7C8aMlfD02vIq4b+WHb0noQ/YYuerNfY=; b=YEGuTXlo1vwRZ+BWGT6vHF0iSgeEinuXJLjhiDEYfAxksYeuNIlEtIymxweDtTaERG yZmg+7JZ+zFPFeGspDVvOWHMtcoVa7GJuBAZQCuNCEyz/FKWhG1GEBqa8nO6VqMW8dhB ddMDpbgXBp3Be+u1c3HwzV49KSof5nEVCStyXsg88hTiHRbmyILYoptzZP7IpxgzjN+p HVuAg1/Cr/A3u3r1KlOo3bYH6mRUPpR/1Jnem4jQ0+fam3YubdyeXmApvFxCgk+y0GXI WEsNEtTj2cBidv+gNp8S5nZbhKMGzo/8bNhMsnUb2cDuWqAWaysBO0lkBoUN6Hm0ERk6 uRgA== X-Gm-Message-State: ACrzQf2Uaz9R2IS6px4NR+Hd78jtfwm+PQ+d4l30Is1IW1DoaByBl1EH IlRj/ywLbCb7QELtpVIQMObcN570aj0m8GchJCcRW5eu1xgCAw== X-Google-Smtp-Source: AMsMyM7SdmAicYgl5UwZ7Frwpkx2iA4hj73WSbFTeCRYeWa5UF+2LnrJ0f7xO+wvbIunt5NWDPqG8l4OFIhx4HIPY7A= X-Received: by 2002:a9d:1781:0:b0:639:39ee:9c4c with SMTP id j1-20020a9d1781000000b0063939ee9c4cmr5175591otj.234.1663449650155; Sat, 17 Sep 2022 14:20:50 -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 01:20:40 +0400 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: Alan Somers Cc: freebsd-fs Content-Type: multipart/alternative; boundary="0000000000007fd3ae05e8e60d4f" X-Rspamd-Queue-Id: 4MVP4M4lHQz43v0 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=Ts1OceD0; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of milkyindia@gmail.com designates 2607:f8b0:4864:20::334 as permitted sender) smtp.mailfrom=milkyindia@gmail.com X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_HAM_LONG(-0.99)[-0.985]; 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]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::334:from]; DKIM_TRACE(0.00)[gmail.com:+]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N --0000000000007fd3ae05e8e60d4f Content-Type: text/plain; charset="UTF-8" On Sun, Sep 18, 2022 at 12:58 AM Alan Somers wrote: > On Sat, Sep 17, 2022 at 2:49 PM milky india wrote: > > > > > > > > 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 < > 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 > 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. > > > --------------------------------------------------------------------------- > > Yes, you normally would not write the ".eli", because "geli resize" is > normally used when geli is not attached. But it seems like you're > currently booted from this device, right? In that case, detaching it > isn't an easy option for you. If you like, you could try automatic > expansion instead. First enable it. If it doesn't automatically > expand when you enable that option, then you may have to "gpart > resize" again. You can enable it with "geli configure -r > /dev/ada0p3". > >Yes, you normally would not write the ".eli", because "geli resize" is > normally used when geli is not attached.But it seems like you're > currently booted from this device, right? Yes - on a live system. > You can enable it with "geli configure -r /dev/ada0p3". Seems to have run without any output : ---------------------------------- geli configure -r /dev/ada0p3 -------------------------------------------- But geli list output hasn't changed apparently ---------------------------------------------------- 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 -------------------------------------------------------------------- Is it supposed to show up after a restart? Or did it just not work? I'm just so lost now - hoping I can even restart the machine and data isn't lost/corrupted :( --0000000000007fd3ae05e8e60d4f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Sep 18, 2022 at 12:58 AM Alan= Somers <asomers@freebsd.org&= gt; wrote:
On Sa= t, Sep 17, 2022 at 2:49 PM milky india <milkyindia@gmail.com> wrote:
>
>
>
> On Sun, Sep 18, 2022 at 12:44 AM Alan Somers <asomers@freebsd.org> wrote:
>>
>> On Sat, 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> wr= ote:
>> >>
>> >> 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> wrote:
>> >> >>
>> >> >> 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 Somer= s <asomers@free= bsd.org> wrote:
>> >> >> >>
>> >> >> >> On Sat, Sep 17, 2022 at 12:52 PM milky = india <milkyin= dia@gmail.com> wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Sat, Sep 17, 2022 at 10:43 PM A= lan Somers <aso= mers@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 rea= d the geli man page. I was specifically warned against using "geli res= ize" since it may not work as expected https://forums.FreeBSD.= org/threads/how-to-extend-zfs-geli-encrypted-disk-space-not-showing.86447/p= ost-581642
>> >> >> >> >> > Is this advise wrong?
>> >> >> >> >> > > "The geli has a= utoresize flag which will handle the new provider size after gpart resize c= ommand."
>> >> >> >> >> > followed by
>> >> >> >> >> > > You are right, no ge= li 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 1= 0:20 PM Alan Somers <asomers@freebsd.org> wrote:
>> >> >> >> >>
>> >> >> >> >> top-posting is where you inser= t your reply above the previous email.
>> >> >> >> >> Bottom posting is where you in= sert your reply below it, like I'm
>> >> >> >> >> doing.=C2=A0 The forum user sa= id that you shouldn't need to run "geli
>> >> >> >> >> resize" because the AUTOR= ESIZE flag is on.=C2=A0 But as you can see from
>> >> >> >> >> your "geli list" out= put, 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 r= ate, you can try it both ways.=C2=A0 You might
>> >> >> >> >> want to make a copy of /var/ba= ckups/ada0p3.eli, just in case you make
>> >> >> >> >> a mistake.
>> >> >> >> >
>> >> >> >> > Thanks - I hope I am bottom postin= g this as was expected of me.
>> >> >> >> >
>> >> >> >> > So if I understand correctly the A= UTORESIZE flag is present for adaop2 and NOT for adap3 (which is the partit= ion we are concerned about) - hence the advice given to not use "geli = resize" isn't applicable here. Am I understanding this correctly?<= br> >> >> >> >>
>> >> >> >> Yes
>> >> >> >>
>> >> >> >> >
>> >> >> >> > > So you need to run "geli= resize"
>> >> >> >> > Is this the only command that I ne= ed to run to resize my geli partition?
>> >> >> >>
>> >> >> >> Yes
>> >> >> >>
>> >> >> >> >
>> >> >> >> > > The "-s" flag shoul= d 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 backu= p 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 th= is works - "geli list" would reflect the size to be 458G? (vs 290= G currently)
>> >> >> >> > And that's the output I can tr= ust to have solved the issue - or is there more to it?
>> >> >> >>
>> >> >> >> Yes.
>> >> >> >
>> >> >> > > The "-s" flag should be unne= cessary since your provider is already online.
>> >> >> > When I try to run "geli resize /dev/ad= a0p3.eli" it complains. So I guess options s is must ? If yes - do I n= eed to put in the exact size down to bytes from the output of geli list ? U= nder "Mediasize" ?
>> >> >> > ---------------------------------------
>> >> >> > geli: Option 's' not specified.
>> >> >> > ---------------------------------------- >> >> >>
>> >> >> Dude, it's easier just to try it, than to as= k us.=C2=A0 Go for it.=C2=A0 The
>> >> >> worst case scenario if you get the argument wron= g 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 i= n a size less than the current size then possibly the data after that get&#= 39;s lost? Or if I put in a size greater than the current size then there i= s 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 gel= i where to find the old
>> >> label, if the provider isn't already attached.=C2=A0 = If you supply the
>> >> wrong argument, then geli won't be able to find the l= abel, and thus
>> >> won't be able to do anything.=C2=A0 It won't dest= roy any data, and it will
>> >> always automatically determine the size of the current pr= ovider.=C2=A0 Of
>> >> course, if you're worried about losing data, you shou= ld always save a
>> >> copy of /var/backups/ada0p3.eli, as I suggested.
>> >> -Alan
>> >
>> >
>> >=C2=A0 >The purpose of the "-s" argument is to te= ll geli where to find the old
>> > > label, if the provider isn't already attached.=C2=A0= 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 e= lse - the man page says it's for the old size - that's why I was tr= ying to figure it out and still haven't been able to quite yet. Althoug= h I suspect the "Mediasize" output for p3 from "geli list&qu= ot; is what 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 provide= r before it was resized.
>> > -------------------------------------------------------------= -----------------------------------
>>
>> Yes, that's right.=C2=A0 geli needs to know the old size of th= e provider 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?
> -----------------------------------------------------------------
> 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.
> ----------------------------------------------------------------------= -----

Yes, you normally would not write the ".eli", because "geli = resize" is
normally used when geli is not attached.=C2=A0 But it seems like you're=
currently booted from this device, right?=C2=A0 In that case, detaching it<= br> isn't an easy option for you.=C2=A0 If you like, you could try automati= c
expansion instead.=C2=A0 First enable it.=C2=A0 If it doesn't automatic= ally
expand when you enable that option, then you may have to "gpart
resize" again.=C2=A0 You can enable it with "geli configure -r /dev/ada0p3".
=C2=A0>Yes, you normally would n= ot write the ".eli", because "geli resize" is
>= normally used when geli is not attached.But it seems like you're
= > currently booted from this device, right?
Yes - on a live system.= =C2=A0

> You can enable it with "geli conf= igure -r /dev/ada0p3".
Seems to have run without any output = :
----------------------------------
geli configure -r = /dev/ada0p3
--------------------------------------------
But geli list output hasn't changed apparently
--------= --------------------------------------------
geli list
Geom na= me: ada0p3.eli
State: ACTIVE
EncryptionAlgorithm: AES-XTS
KeyLengt= h: 256
Crypto: accelerated software
Version: 7
UsedKey: 0
Flags= : BOOT, GELIBOOT
KeysAllocated: 73
KeysTotal: 73
Providers:
1. = Name: ada0p3.eli
=C2=A0 =C2=A0Mediasize: 311481593856 (290G)
=C2=A0 = =C2=A0Sectorsize: 4096
=C2=A0 =C2=A0Mode: r1w1e1
Consumers:
1. Nam= e: ada0p3
=C2=A0 =C2=A0Mediasize: 491516858368 (458G)
=C2=A0 =C2=A0Se= ctorsize: 512
=C2=A0 =C2=A0Stripesize: 0
=C2=A0 =C2=A0Stripeoffset: 8= 590983168
=C2=A0 =C2=A0Mode: r1w1e1

Geom name: ada0p2.eli
--------------------------------------------------------------------=
Is it supposed to show up after a restart?=C2=A0
Or di= d it just not work?
I'm just so lost now - hoping I can even = restart the machine and data isn't lost/corrupted :(
--0000000000007fd3ae05e8e60d4f--