public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximilian Hill <mhill@inett.de>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: aderumier@odiso.com, pve-devel <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] ceph create pool with min_size=1 not possible anymore with last gui wizard
Date: Mon, 7 Jun 2021 11:42:59 +0200	[thread overview]
Message-ID: <YL3qI17b4tYr6KzY@inett.de> (raw)
In-Reply-To: <c1890524-65c2-206f-0add-747c7d1979a0@proxmox.com>

[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]

Hi,

On Mon, Jun 07, 2021 at 09:14:13AM +0200, Dominik Csapak wrote:
> On 6/7/21 08:57, aderumier@odiso.com wrote:
> > Le vendredi 04 juin 2021 à 15:23 +0200, Dominik Csapak a écrit :
> > > On 6/4/21 04:47, aderumier@odiso.com <mailto:aderumier@odiso.com> wrote:
> > > > I was doing a training week with students,
> > > > 
> > > > and I see that the new ceph wizard to create pool don't allow to set
> > > > min_size=1 anymore.
> > > > 
> > > > It's currently displaying a warning "min_size <= size/2 can lead to
> > > > data loss, incomplete PGs or unfound objects",
> > > > 
> > > > that's ok  ,  but It's also blocking the validation button.
> > > > 
> > > 
> > > yes, in our experience, setting min_size to 1 is always a bad idea
> > > and most likely not what you want
> > > 
> > > what is possible though is to either create the pool on the cli,
> > > or changing the min_size after creation to 1 (this is not blocked)
> > > 
> > yes, Sute. I could be great to be able to change size/min_size from the
> > gui too.
> > 
> > 
> 
> this should already possible in current versions, but as i said
> not for pool creation, only afterwards
> 

In my opinion, setting min_size below 2 and size below 3 shouldn't be
possible at all. Both shouldn't be done unless you really know what you're
doing. At that point, you know enough about Ceph to just type that one
command.

That has nothing to do with an easy and safe Ceph setup and the
possibility in itself might lead to unseafe setups by users without
enough knowlege about Ceph.

Maybe a strong opinion, but --yes-i-really-mean-it


Max

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-06-07  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  2:47 aderumier
2021-06-04 13:23 ` Dominik Csapak
2021-06-07  6:57   ` aderumier
2021-06-07  7:14     ` Dominik Csapak
2021-06-07  9:42       ` Maximilian Hill [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=YL3qI17b4tYr6KzY@inett.de \
    --to=mhill@inett.de \
    --cc=aderumier@odiso.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=pve-devel@pve.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