From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, "Max R. Carrara" <m.carrara@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-manager master v1] fix #6747: ceph: osd: swap vg and lv arguments when creating an OSD
Date: Tue, 2 Sep 2025 14:32:09 +0200 [thread overview]
Message-ID: <175681632554.470789.4434813069812786109.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250902104119.110464-1-m.carrara@proxmox.com>
On Tue, 02 Sep 2025 12:41:16 +0200, Max R. Carrara wrote:
> ... specifically when creating logical volumes for OSD DB / WAL devices,
> if the block device wasn't in use beforehand.
>
> The original line was part of a fix for #6652 (92bbc0c89fe) and
> slipped through during testing.
>
>
> [...]
Applied, thanks!
[1/1] fix #6747: ceph: osd: swap vg and lv arguments when creating an OSD
commit: eecc7a25a501caf751bf6af5df2b173e6ad2ca0f
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-09-02 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 10:41 [pve-devel] " Max R. Carrara
2025-09-02 12:32 ` Fabian Grünbichler [this message]
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=175681632554.470789.4434813069812786109.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=m.carrara@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