public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Friedrich Weber <f.weber@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager] postinst: Filter RADOS block devices
Date: Thu, 14 Dec 2023 10:34:57 +0100	[thread overview]
Message-ID: <ce79c850-6122-4537-bff7-3a5b13270b57@proxmox.com> (raw)
In-Reply-To: <de553850-b849-4112-9fa5-bfc4da2e5f67@proxmox.com>

Already discussed with Stefan off-list yesterday, posting here for the
record:

There is one problem when upgrading from < 8.1.4 with a custom LVM
config where global_filter spans multiple lines, e.g.:

devices {
     # added by pve-manager to avoid scanning ZFS zvols
     global_filter=["r|/dev/zd.*|",
		"r|/dev/foobar|"]
}

With the patch, this is rewritten but only the first line is commented out:

devices {
     # added by pve-manager to avoid scanning ZFS zvols
#     global_filter=["r|/dev/zd.*|",
		"r|/dev/foobar|"]
 }
devices {
     # added by pve-manager to avoid scanning ZFS zvols and RADOS block
devices
     global_filter=["r|/dev/zd.*|","r|/dev/rbd.*|"]
 }

And LVM doesn't like this:

# lvs
Parse error at byte 111808 (line 2453): unexpected token
  Failed to load config file /etc/lvm/lvm.conf

Not sure how we could extend the global_filter in a reliable way if it
is customized ... worst case, it might be an option to only rewrite the
LVM config if it is unchanged (plus our ZFS zvol addition), and leave
custom configs alone (and add a hint in the upgrade guide)?




  reply	other threads:[~2023-12-14  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 15:35 Stefan Hanreich
2023-12-13 17:07 ` Stefan Hanreich
2023-12-14  9:34   ` Friedrich Weber [this message]
2023-12-14  9:55     ` Stefan Hanreich
2023-12-14  9:56       ` Stefan Hanreich
2023-12-14 10:17         ` Friedrich Weber

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=ce79c850-6122-4537-bff7-3a5b13270b57@proxmox.com \
    --to=f.weber@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal