all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager master v1 2/2] fix #6652: d/postinst: enable autoactivation for Ceph OSD LVs
Date: Wed, 13 Aug 2025 11:02:52 +0200	[thread overview]
Message-ID: <1755075719.refr4vlkgq.astroid@yuna.none> (raw)
In-Reply-To: <DC1669I01FP4.21QC66DHX63TY@proxmox.com>

On August 13, 2025 10:50 am, Max R. Carrara wrote:
> On Wed Aug 13, 2025 at 9:52 AM CEST, Fabian Grünbichler wrote:
>> On August 12, 2025 6:46 pm, Max R. Carrara wrote:
>> > Introduce a new helper command pve-osd-lvm-enable-autoactivation,
>> > which gracefully tries to enable autoactivation for all logical
>> > volumes used by Ceph OSDs while also activating any LVs that aren't
>> > active yet. Afterwards, the helper attempts to bring all OSDs online.
>>
>> I think this is probably overkill - this only affects a specific non
>> standard setup, the breakage is really obvious, and the fix is easy:
>> either run lvchange on all those LVs, or recreate the OSDs after the fix
>> for creation is rolled out..
>>
>> i.e., the fallout from some edge cases not being handled correctly in
>> the 200 line helper script here is probably worse than the few setups
>> that run into the original issue that we can easily help along
>> manually..
> 
> I mean, this script doesn't really do much, and the LVs themselves are
> fetched via `ceph-volume` ... But then again, you're probably right that
> it might just break somebody else's arcane setup somewhere.
> 
> As an alternative, I wouldn't mind writing something for the release
> notes' known issues section (or some other place). Assuming a standard
> setup*, all that the user would have to do is identical to what the
> script does, so nothing too complicated.

but the known issue will be gone, except for the handful of users that
ran into it before the fix was rolled out.. this is not something you
noticed 5 months later?

> (*OSDs with WAL + DB on disks / partitions without anything else inbetween)

I am not worried about the script breaking things, but about it printing
spurious errors/warnings for unaffected setups.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  parent reply	other threads:[~2025-08-13  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 16:46 [pve-devel] [PATCH pve-manager master v1 0/2] Fix #6652: LVM Autoactivation Missing " Max R. Carrara
2025-08-12 16:46 ` [pve-devel] [PATCH pve-manager master v1 1/2] fix #6652: ceph: osd: enable autoactivation for OSD LVs on creation Max R. Carrara
2025-08-13  7:48   ` Fabian Grünbichler
2025-08-13  8:28     ` Max R. Carrara
2025-08-12 16:46 ` [pve-devel] [PATCH pve-manager master v1 2/2] fix #6652: d/postinst: enable autoactivation for Ceph OSD LVs Max R. Carrara
2025-08-13  7:52   ` Fabian Grünbichler
2025-08-13  8:50     ` Max R. Carrara
2025-08-13  9:01       ` Friedrich Weber
2025-08-13  9:02       ` Fabian Grünbichler [this message]
2025-08-13  9:40         ` Max R. Carrara
2025-08-13 10:05           ` Fabian Grünbichler
2025-08-13 13:43 ` [pve-devel] superseded: [PATCH pve-manager master v1 0/2] Fix #6652: LVM Autoactivation Missing " Max R. Carrara

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=1755075719.refr4vlkgq.astroid@yuna.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal