From nobody Sat Sep 17 18:57:53 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 4MVKvf0yysz4c5D1 for ; Sat, 17 Sep 2022 18:58:06 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (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 4MVKvd365zz3m74 for ; Sat, 17 Sep 2022 18:58:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-qt1-f180.google.com with SMTP id f26so15701611qto.11 for ; Sat, 17 Sep 2022 11:58:05 -0700 (PDT) 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=W6oGFoV0Zbb5YOktR5V5WZdUc5cbC4JtXJtMQI45SFw=; b=zNz9/UpcDAr+y3Vpla9R2sEe9Z9puv4LzBw+bVSQM9cJbwn2eRSbXUxl5C7ZXiiRBb lOVoSh/DRJ3bF7zxobaU0nAu+eP+vviQq8mENEGsiQtXoOP2s9IsuU8ew3CUNQlD0sd1 RXhY79sn+TvLnuAC8+l2mLhLruNqbnNwt67CzkuM+gkJkJKpRNLER8sm+rC514NCEGuS FtIWdZ/HN0zFQP7Ukz8UmOCBQD2ng8JceFXOB7l8JMi3khknpuBDLkiYRo4Ykt+FLiou iyB4DJ4HFDWPjeKkRsy/Po7/fAYNG3qKsav8pBSaH0foierhadqJ3ueI12ysJgAOuyGd v7Dg== X-Gm-Message-State: ACrzQf3jFYH6/vd/IdOl8W/dQtmnKWnf/RDv+cl1yrCpwPQoY0N2TQGN +zi+9Tp/Lg6uKRcbS0RhpZ3fqNaSjpHSvk1adqdxkI3+ X-Google-Smtp-Source: AMsMyM5WASp3+2ShfdTSkt0Bj38vk8W9xGReIta7w47r9oDnCET7A1pDHN0cNeDtiLnjvHRcaU/eU2EhFfUVKSpxYj8= X-Received: by 2002:a05:622a:4b:b0:35b:a15d:19dd with SMTP id y11-20020a05622a004b00b0035ba15d19ddmr9273392qtw.52.1663441084757; Sat, 17 Sep 2022 11:58:04 -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: Alan Somers Date: Sat, 17 Sep 2022 12:57:53 -0600 Message-ID: Subject: Re: Need help with live system expansion (zfs+geli) To: milky india Cc: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4MVKvd365zz3m74 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.160.180 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.07 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; NEURAL_HAM_LONG(-0.99)[-0.993]; NEURAL_HAM_SHORT(-0.98)[-0.975]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.160.180:from]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.160.180:from]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[asomers]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N 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.