public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com, Parker Wahle <regulad@regulad.xyz>
Subject: Re: [PATCH manager] fix #8193: ceph: pool set: keep min_size when changing size
Date: Thu, 29 Oct 2026 09:42:31 +0800	[thread overview]
Message-ID: <20261029014231.3018868-1-k.chai@proxmox.com> (raw)
In-Reply-To: <20261018205203.654-2-regulad@regulad.xyz>

On Sun Oct 18, 2026 at 10:52 PM CEST, Parker Wahle wrote:
[snip]
> @@ -304,6 +304,8 @@ sub set_pool {
>              print "$err";
>          } else {
>              delete $param->{$setting};
> +            # Ceph resets min_size when size changes, so re-read before comparing the rest
> +            $current_properties = get_pool_properties($pool, $rados) if $setting eq 'size';
>          }
>      }

Thanks for tracking this down! I could reproduce it on a three-node
lab cluster running Ceph 21.1.2, with osd_pool_default_min_size = 2.
Without the patch, both of your examples lose the requested min_size:

- a 2/1 pool set to size=3 min_size=1 ends up with min_size 2
- a 4/3 pool set to size=3 min_size=3 ends up with min_size 2

With the patch, both keep the min_size that was asked for. I also
tried changing only the size, which still gives Ceph's default
min_size, and changing only min_size, which works as before. The pool
is only re-read when the size actually changes, which seems fine to
me.

Tested-by: Kefu Chai <k.chai@proxmox.com>
Reviewed-by: Kefu Chai <k.chai@proxmox.com>




      reply	other threads:[~2026-10-29  1:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 20:52 SPAM: [PATCH manager] fix #8193: ceph: pool set: keep min_size when changing size Parker Wahle
2026-10-29  1:42 ` Kefu Chai [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=20261029014231.3018868-1-k.chai@proxmox.com \
    --to=k.chai@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=regulad@regulad.xyz \
    /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