From nobody Sat Sep 17 20:41:59 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 4MVNCl2YMwz4cPFg for ; Sat, 17 Sep 2022 20:42:11 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: from mail-oa1-x36.google.com (mail-oa1-x36.google.com [IPv6:2001:4860:4864:20::36]) (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 4MVNCk4vHRz3ylS; Sat, 17 Sep 2022 20:42:10 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-11e9a7135easo56888415fac.6; Sat, 17 Sep 2022 13:42:10 -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=+CptSgWP/xTMh6PNnDyf8svv7ak18mXo/A62mvNZZIM=; b=Aci3Cg/U8m81+PrUn5h8QYpyAS+wcX0emDwWGp/sweVbzNBAacjko/2CnNJb442QlR k+sttGk0Qz3clOrON7yhGyMtJO+Zg9VJPVIjUi39Lb8hAnwdBVGPz94FsUpBDJc7nzcI GqXE3KJ4L1+B3R/HGseeEBBQhKxj1XW4qhJyPhA9K2y6Iy0xnCkhIv4Ms5pYmftpp09T xHDtz5QTleVF0+ERJMKEL/f/1hyyMUwmO3QD/ion7Vdt+bVrK7yDsBo0Osc8/dELwgQl 9TJFASTTmAYca60nqp6IV5zK/H8t7Bct69s9t2hnjKa4CmOx1DYLlhb5f7pMvsi76jz4 BAkw== 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=+CptSgWP/xTMh6PNnDyf8svv7ak18mXo/A62mvNZZIM=; b=1wfxmwLqyXJa3fuYoqZjxsOW+txlmDC1YJ8WnD+eHGzhqaDf6xZM/IlGwjykM33NxG 9l3iVcEpZcVu5FV20sIQA6LU6Wj4dQ+dIxGllreI3ClQB0wGuQJJ6zaFbtO6ED26Jv0L yuq3ifX5AFJESwwW2FbMRlZ5kfStp7PUeZCj174HIlIWnNQa4VCfdISIQ59WhBlJEQvM 79Hb/unb8vYX220wHo82lKLod54y3OdW0FDpEhDbhP62vN4b68/+Z+PuUqJT+apYGO/x zxN42k0c/nNovqcTmEe3DUo2DOf33Uh7g+VUavar0tZepOunO5Tze7Z/rK/439YSfo96 BJkQ== X-Gm-Message-State: ACgBeo3YZxYTXEVTdPHQRZ8roTlc3vfrFiBL/kp3XRSMTwVaCZ70id8p BtXcCcYCjyBbfc95Xx8BSOc70vfvycNY35sRQyvBE8AOeROJTA== X-Google-Smtp-Source: AA6agR7T9+ZDxjhmnVEU0XQpe5UXan6eui5KB63NV8B+WpP4+QpI3+nXhFhyz3fjQu3BQ99IULg6ZRHfPi3KZnhTUUA= X-Received: by 2002:a05:6871:b2a:b0:12b:91ce:e45b with SMTP id fq42-20020a0568710b2a00b0012b91cee45bmr11775485oab.291.1663447328822; Sat, 17 Sep 2022 13:42: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:41:59 +0400 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: Alan Somers Cc: freebsd-fs Content-Type: multipart/alternative; boundary="00000000000023199805e8e58366" X-Rspamd-Queue-Id: 4MVNCk4vHRz3ylS X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b="Aci3Cg/U"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of milkyindia@gmail.com designates 2001:4860:4864:20::36 as permitted sender) smtp.mailfrom=milkyindia@gmail.com X-Spamd-Result: default: False [-3.80 / 15.00]; NEURAL_HAM_SHORT(-0.98)[-0.978]; NEURAL_HAM_MEDIUM(-0.94)[-0.942]; NEURAL_HAM_LONG(-0.88)[-0.885]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860: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:2001:4860:4864::/48, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::36: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 --00000000000023199805e8e58366 Content-Type: text/plain; charset="UTF-8" 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 > wrote: > >> >> > > >> >> > > >> >> > > >> >> > On Sat, Sep 17, 2022 at 10:43 PM Alan Somers > 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. ------------------------------------------------------------------------------------------------ --00000000000023199805e8e58366 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Sep 18, 2022 at 12:30 AM Alan= Somers <asomers@freebsd.org&= gt; wrote:
On Sa= t, 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 Somers <asomers@freebsd.org> wr= ote:
>> >>
>> >> 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 pag= e. 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 whi= ch will handle the new provider size after gpart resize command."
>> >> >> > followed by
>> >> >> > > You are right, no geli resize needed.<= br> >> >> >> >
>> >> >> > What would be the correct sequence of comma= nds 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 Somer= s <asomers@free= bsd.org> wrote:
>> >> >>
>> >> >> top-posting is where you insert your reply above= the previous email.
>> >> >> Bottom posting is where you insert your reply be= low it, like I'm
>> >> >> doing.=C2=A0 The forum user said that you should= n't need to run "geli
>> >> >> resize" because the AUTORESIZE flag is on.= =C2=A0 But as you can see from
>> >> >> your "geli list" output, it's actu= ally off.=C2=A0 So you need to run "geli
>> >> >> resize".=C2=A0 The "-s" flag shou= ld be unnecessary since your provider is
>> >> >> already online.=C2=A0 At any rate, you can try i= t both ways.=C2=A0 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 expe= cted of me.
>> >> >
>> >> > So if I understand correctly the AUTORESIZE flag is = present for adaop2 and NOT for adap3 (which is the partition we are concern= ed about) - hence the advice given to not use "geli resize" isn&#= 39;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 resiz= e my geli partition?
>> >>
>> >> Yes
>> >>
>> >> >
>> >> > > The "-s" flag should be unnecessary s= ince your provider is
>> >> > already online.
>> >> > Ok thanks.
>> >> >
>> >> > >You might want to make a copy of /var/backups/ad= a0p3.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 t= o do that, but it isn't
>> >> strictly necessary.
>> >>
>> >> >
>> >> > I suppose at the end of it - if this works - "g= eli 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 "Mediasi= ze" ?
>> > ---------------------------------------
>> > 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<= br> >> happens.
>
>
> > The worst case scenario if you get the argument wrong is that not= hing 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 gel= i 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. Th= at'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 th= e old
label, if the provider isn't already attached.=C2=A0 If you supply the<= br> 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 data, 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 &quo= t;-s" argument is to tell 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 argum= ent with something else - the man page says it's for the old size - tha= t's why I was trying to figure it out and still haven't been able t= o quite yet. Although I suspect the "Mediasize" output for p3 fro= m "geli list" is what the s value should be - but not very sure :=
-----------------------------------------------------------------------= -------------------
Additional options incl= ude:

=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=A0The size of the provider befor= e it was resized.
---------------------= ---------------------------------------------------------------------------=

--00000000000023199805e8e58366--