From nobody Sat Sep 17 20:24:57 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 4MVMr52chsz4cLLK for ; Sat, 17 Sep 2022 20:25:09 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 4MVMr44nScz3w4T; Sat, 17 Sep 2022 20:25:08 +0000 (UTC) (envelope-from milkyindia@gmail.com) Received: by mail-oi1-x231.google.com with SMTP id w125so10132245oig.3; Sat, 17 Sep 2022 13:25:08 -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=Cr/k7a4Pa38/FaxguXKaZ+fBgh77mkwpFQAsJ4s/waQ=; b=FFz3QCTuF5vMS1MvSlFR3DXt+CNK9PCTCY2HpNQ2N349+xGoV+kxNUJGN//nstxeSC ows+vGlQjtmCKZ3O0FDyY/+9/mNeaPerReMbn10R2nxjiUoZjrEQboprOBQkK0Wry65m YxkzHzR9iuFriNqFLl9c7dCOTxaLDUQzzZ8oE7da5JMlflCS/bqmMr4XX3FyuLHaj/0O aDfnUxhh7tHfnCyVmzy7EfhQGR1yiMyf7giI7wM/c8/MfE7QmSX4PkJ9oG1Yoz9lABST 7fz4/OJNwtSl+cGOgrulg3Yyo8Hmk8nR4Dt+HrNKVCHvmJ7R4n/a/tx2GLARAC2ci1Uz s60w== 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=Cr/k7a4Pa38/FaxguXKaZ+fBgh77mkwpFQAsJ4s/waQ=; b=jJb8xo8DCgP9MOLWwnLx3R8uzamdRoSArwiFB+e2yrfJ9FNnrNvfs5W7uiwsYyQd5x 85p3KMj+PgIBgMdfRQAt80+pQas25vV0Ctfqz3wa6dzjqcDP2DZE3g39xGTvp2KYEI40 JuUN20NDFw5YHAFuQ0hJxNoGFGJDqJEG1UiVI6f5Ss2lt79KKmqZDuW55/n3gSt2dwYd d/2NQjv70CN9qGT/NiBrVOjnstSWoYr8LykmVGK9N1fxANg7xxtE/guQBWXThNiph1lK 1Gj+KPqQOFMKCnuximVKyg32/tBLPjJ5I3z55NQQk4RUGD3FxvmIxBzREAd2cSttRTj/ ujkw== X-Gm-Message-State: ACgBeo3Qho3Ix2pRD4M57QHikqXWi+uZ+zLhneONicHzOkdmcYm5gWLo zRYJCGOExV66YtL8AhGoboj79w636zxu6LG5GkUf3XhKj7v8/w== X-Google-Smtp-Source: AA6agR4T4GgSmYjic6Aw1uLT6REgLlvdsgXiG6cRF8a8V2U3IVQ+Snt/HVGLj9byBEYZmfbREklDWtgiVVixoIpcdBM= X-Received: by 2002:a54:4495:0:b0:350:2a7:600f with SMTP id v21-20020a544495000000b0035002a7600fmr9174137oiv.291.1663446307583; Sat, 17 Sep 2022 13:25:07 -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:24:57 +0400 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: Alan Somers Cc: freebsd-fs Content-Type: multipart/alternative; boundary="000000000000443cc005e8e54696" X-Rspamd-Queue-Id: 4MVMr44nScz3w4T X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=FFz3QCTu; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of milkyindia@gmail.com designates 2607:f8b0:4864:20::231 as permitted sender) smtp.mailfrom=milkyindia@gmail.com X-Spamd-Result: default: False [-3.83 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.993]; NEURAL_HAM_MEDIUM(-0.94)[-0.944]; NEURAL_HAM_LONG(-0.89)[-0.890]; 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::231: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 --000000000000443cc005e8e54696 Content-Type: text/plain; charset="UTF-8" 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 > 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. > > ---------------------------------------- > > 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. --000000000000443cc005e8e54696 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Sep 18, 2022 at 12:20 AM Alan= Somers <asomers@freebsd.org&= gt; wrote:
On Sa= t, 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 Somers <asomers@freebsd.org> wr= ote:
>> >>
>> >> 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-z= fs-geli-encrypted-disk-space-not-showing.86447/post-581642
>> >> > Is this advise wrong?
>> >> > > "The geli has autoresize flag which will h= andle 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 fi= x this - Simply "geli resize" ? (the -s option seems to be additi= onal, 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 prev= ious email.
>> >> Bottom posting is where you insert your reply below it, l= ike I'm
>> >> doing.=C2=A0 The forum user said that you shouldn't n= eed to run "geli
>> >> resize" because the AUTORESIZE flag is on.=C2=A0 But= as you can 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 unn= ecessary since your provider is
>> >> already online.=C2=A0 At any rate, you can try it both wa= ys.=C2=A0 You might
>> >> want to make a copy of /var/backups/ada0p3.eli, just in c= ase you make
>> >> a mistake.
>> >
>> > Thanks - I hope I am bottom posting this as was expected of m= e.
>> >
>> > So if I understand correctly the AUTORESIZE flag is present f= or adaop2 and NOT for adap3 (which is the partition we are concerned about)= - hence the advice given to not use "geli resize" isn't appl= icable 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.=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&= quot; would reflect the size to be 458G? (vs 290G currently)
>> > And that's the output I can trust to have solved the issu= e - 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 siz= e 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.=C2=A0 Go for it.=C2= =A0 The
worst case scenario if you get the argument wrong is that nothing
happens.

--000000000000443cc005e8e54696--