From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 1/2] postinst: set custom LVM settings
Date: Tue, 22 Jun 2021 12:23:25 +0200 [thread overview]
Message-ID: <1624357320.sqo7goqoxp.astroid@nora.none> (raw)
In-Reply-To: <20210622101657.2344347-1-f.gruenbichler@proxmox.com>
On June 22, 2021 12:16 pm, Fabian Grünbichler wrote:
> now that we no longer ship our own LVM packages, set the relevant
> filtering options here if they are missing.
>
> for an upgrade from PVE 6.x, the following two scenarios are likely:
>
> A: user edited config provided by our old lvm2 package. it likely
> contains our (or a modified) global_filter, but the old scan_lvs
> default. in this case we ignore global_filter as long as it contains our
> 'don't scan zvols' entry, and set scan_lvs to false.
>
> B: config provided by our old lvm2 package was taken over by default
> config from stock lvm2 package. scan_lvs defaults to false already, but
> global_filter is unset (scan everything), so we need to set our own
> global_filter excluding zvols.
>
> other combinations should be handled fine as well.
>
> for new installs (installer, install on top of Debian Bullseye) we are
> always in scenario B.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
>
> Notes:
> once other difference between our old config and the stock one is that we had
> 'issue_discards' enabled. we could either put this in the release notes, or
> also enable it here automatically - but it is less straight-forward since the
> default is not "almost certainly wrong" like for the filtering options..
>
> we could drop the "check for marker" and just do this once on initial install
> and upgrades from 6.x, but since the fallout from not having these in place can
> be data corruption (activating multiple VGs with same name, using one from a
> guest on the host!) I'd rather play it safe..
>
> debian/postinst | 55 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/debian/postinst b/debian/postinst
> index dcf77d24..241aac08 100755
> --- a/debian/postinst
> +++ b/debian/postinst
> @@ -8,6 +8,58 @@ set -e
> # done its automatic conffile handling, and all the packages we depend
> # of are already fully installed and configured.
>
> +LVM_CONF_MARKER="# added by pve-manager to avoid scanning"
> +
> +set_lvm_conf() {
> + OLD_VALUE="$(lvmconfig --typeconfig full devices/global_filter)"
> + NEW_VALUE='global_filter=["r|/dev/zd.*|"]'
> +
> + # only do these changes once
> + # keep user changes afterwards provided marker is still there..
> + if grep -qv "$LVM_CONF_MARKER" /etc/lvm/lvm.conf; then
> + # check global_filter
> + # keep previous setting from our custom packaging if it is still there
> + if echo "$OLD_VALUE" | grep -qvF 'r|/dev/zd.*|'; then
> + SET_FILTER=1
> + BACKUP=1
> + fi
> + # should be the default since bullseye
> + if lvmconfig --typeconfig full devices/scan_lvs | grep -qv 'scan_lvs=0'; then
> + SET_SCAN_LVS=1
> + BACKUP=1
> + fi
> + if test -n "$BACKUP"; then
> + echo "Backing up lvm.conf before setting pve-manager specific settings.."
> + cp -vb /etc/lvm/lvm.conf /etc/lvm/lvm.conf.bak
> + fi
> + if test -n "$SET_FILTER"; then
> + echo "Setting 'global_filter' in /etc/lvm/lvm.conf to prevent zvols from being scanned:"
> + echo "$OLD_VALUE => $NEW_VALUE"
> + # comment out existing setting
> + sed -i -e 's/^\([[:space:]]*global_filter[[:space:]]*=\)/#\1/' /etc/lvm/lvm.conf
> + # add new section with our setting
> + cat >> /etc/lvm/lvm.conf <<EOF
> +devices {
> + $LVM_CONF_MARKER ZFS zvols
> + global_filter=$NEW_VALUE
this should of course not have the 'global_filter=' prefix (moved that
into NEW_VALUE before sending and forgot to update this line :-/), but
rather be just
+ $NEW_VALUE
> +}
> +EOF
> + fi
> + if test -n "$SET_SCAN_LVS"; then
> + echo "Adding scan_lvs=0 setting to /etc/lvm/lvm.conf to prevent LVs from being scanned."
> + # comment out existing setting
> + sed -i -e 's/^\([[:space:]]*scan_lvs[[:space:]]*=\)/#\1/' /etc/lvm/lvm.conf
> + # add new section with our setting
> + cat >> /etc/lvm/lvm.conf <<EOF
> +devices {
> + $LVM_CONF_MARKER LVM volumes
> + scan_lvs=0
> +}
> +EOF
> + fi
> + fi
> +}
> +
> case "$1" in
> triggered)
> # We don't print a status message here, as dpkg already said
> @@ -86,6 +138,9 @@ case "$1" in
> newaliases || true
> fi
> fi
> +
> + set_lvm_conf
> +
> ;;
>
> abort-upgrade|abort-remove|abort-deconfigure)
> --
> 2.30.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
next prev parent reply other threads:[~2021-06-22 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 10:16 Fabian Grünbichler
2021-06-22 10:16 ` [pve-devel] [PATCH manager 2/2] postinst: remove outdated calls Fabian Grünbichler
2021-06-22 15:25 ` [pve-devel] applied: " Thomas Lamprecht
2021-06-22 10:23 ` Fabian Grünbichler [this message]
2021-06-22 15:23 ` [pve-devel] [PATCH manager 1/2] postinst: set custom LVM settings Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1624357320.sqo7goqoxp.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox