From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH ceph master v1] pybind/rbd: disable on_progress callbacks to prevent MGR segfaults
Date: Wed, 10 Sep 2025 09:00:03 +0200 [thread overview]
Message-ID: <1757487297.c08wh8yz7v.astroid@yuna.none> (raw)
In-Reply-To: <20250909170515.606422-1-m.carrara@proxmox.com>
On September 9, 2025 7:05 pm, Max R. Carrara wrote:
> Currently, *all* MGRs collectively segfault on Ceph v19.2.3 running on
> Debian Trixie if a client requests the removal of an RBD image from
> the RBD trash (#6635 [0]).
>
> After a lot of investigation, the cause of this still isn't clear to
> me; the most likely culprit are some internal changes to Python
> sub-interpreters that happened between Python versions 3.12 and 3.13.
>
> What leads me to this conclusion is the following:
> 1. A user on our forum noted [0] that the issue disappeared as soon as
> they set up a Ceph MGR inside a Debian Bookworm VM. Bookworm has
> Python version 3.11, before any substantial changes to
> sub-interpreters [1][2] were made.
did you try with stock Debian Trixie packages (the Ceph version is still
18.2 there, which might help narrowing it down)?
in any case, it would be good to bring this issue to upstream's
attention as well!
> 2. There is an upstream issue [3] regarding another segfault during
> MGR startup. The author concluded that this problem is related to
> sub-interpreters and opened another issue [4] on Python's issue
> tracker that goes into more detail.
>
> Even though this is for a completely different code path, it shows
> that issues related to sub-interpreters are popping up elsewhere
> at the very least.
did you try reproducing that one? it seems it requires an optional
ceph-mgr plugin that we have packaged as well, so should be fairly
straight-forward..
_______________________________________________
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:[~2025-09-10 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 17:05 Max R. Carrara
2025-09-10 7:00 ` Fabian Grünbichler [this message]
2025-09-10 7:54 ` Max R. Carrara
2025-09-10 8:54 ` [pve-devel] superseded: " 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=1757487297.c08wh8yz7v.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.