Date: Sat, 17 Sep 2022 12:57:53 -0600 From: Alan Somers <asomers@freebsd.org> To: milky india <milkyindia@gmail.com> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: Need help with live system expansion (zfs+geli) Message-ID: <CAOtMX2h-adnaupXrwH90HpepnnBpUZFY5OaF_e6a91vFCe8Vjw@mail.gmail.com> In-Reply-To: <CACQUA7=6YTN027oUa9xDPNc8Y1MS4rtVYwCxsc0HLpJ8G%2BC8yQ@mail.gmail.com> References: <CACQUA7kC1E%2BHTEAFY=o%2BFpRcfmhJ-qPWuXseNvT5eJzK4Bcdpw@mail.gmail.com> <CAOtMX2g%2BGZ6SjQQPu-YWJhttYS3D7YhU-kAqMY4xHxXoe6rdVg@mail.gmail.com> <CACQUA7nD2Hrkvo5P7_9gyWkJwX8-ZhMAc3HdgrzTCK=XVqRMog@mail.gmail.com> <CAOtMX2iDg3H75Jp5-N5MgLAvBHKFs8UXvCVPBi_YQKMqYWsz6g@mail.gmail.com> <CACQUA7mzfvwRVhc00kGk3rZHKhFtMChZ983EJ0OBn90DJfaMUQ@mail.gmail.com> <CAOtMX2ijrHuhh8E=M%2BD=FKXq9c0tbOq-ZDNRQZ4n32U5=dEaVg@mail.gmail.com> <CACQUA7nTyT9hpguEbQ1LskHJxq1OUckswbpD__Fov-G9t8Myxg@mail.gmail.com> <CAOtMX2gLaur3c8TATuVeZdDNPoLcG%2B4BrTgOp=Ow3jAuStkKtA@mail.gmail.com> <CACQUA7=6YTN027oUa9xDPNc8Y1MS4rtVYwCxsc0HLpJ8G%2BC8yQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2h-adnaupXrwH90HpepnnBpUZFY5OaF_e6a91vFCe8Vjw>