From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 5D48674D61 for ; Fri, 4 Jun 2021 04:48:06 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4F6EF17BEE for ; Fri, 4 Jun 2021 04:48:06 +0200 (CEST) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3EA2817BE3 for ; Fri, 4 Jun 2021 04:48:04 +0200 (CEST) Received: by mail-wm1-x334.google.com with SMTP id f17so4489214wmf.2 for ; Thu, 03 Jun 2021 19:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:user-agent:mime-version :content-transfer-encoding; bh=XrAxRukkxGeHoOqq7bGU/SOVsLft+q5RZT3R8BoN+Vk=; b=0yfJFATEJJVtcPMVgiGLN+pRyaSpz35QG7cEfSNJhBGAq2xsC3/x1MkuWoFo+iMvTq fXoXOCtSExBSa4PPQ0gsZjrQWYpd8j/79uKwokEacqEQxumPxpF65Ryst3LsqpIyL+GZ ZH10lpGRLqKVGTlqpBzKDAqPG6FmK0cd3Z5mZuClajwONpGWC710TR4N9jr+BwqAErKU CI7/2Kw5cOXdDqFGrHJmwqT/Ndfe0CBwNixyx5HiX1qNoIxKYcuAcDvkPLAp3DMwvB8b M27NMw3B1R82HT6VcBRtQOEwmXh2nb2IomjsLX2ohq4RCdX211YlRp6XqLk1zbG7U3qW nHwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:user-agent :mime-version:content-transfer-encoding; bh=XrAxRukkxGeHoOqq7bGU/SOVsLft+q5RZT3R8BoN+Vk=; b=FwNVqtB9x7JUxbSd6fPpWodDjVARSWi6CXPDFauX+u2xxNJBJ+3yCvRCXTcMqwzMky 7+jvKCZohkKv/okJulP5hR3phj9PeiLbP1hJsG/D5Ukwjdg12LzfbttFqAk+RHAL8nRl 5ZsvKEJ+QQdigM4HjTG3yCPl3FUYqbVwPsLO/whBlNdbFMpJkb69bo8TB5jM7OltZXQ3 jcvOt9en10dvLwDGKqZl4Dh2VT9xbVyc38Ruwc0GOHy9Nuknym3n03fwRlaBJiVqvx8j 8wq9FCsexFVT0Uq11FQgKziECZ/VlUgtHpNJip0v0u/BKensTGxS8z3W+0SUdsUdI5hw xBWQ== X-Gm-Message-State: AOAM532Ozi/uYyl07jDO0TQd1UCPXFWJAJ/jkZqDCcpT2AOcAA43HYl2 FU7l2Ohzh/NwEoOQAr2d4zQB/b+r/bDPEqlp X-Google-Smtp-Source: ABdhPJz8ys9r5oNKkve/cQ53tEsL8fnbdJzkF3aDyxKwFc89KgC+t6HkWChgRFdFYYwz7dzYAoY/SA== X-Received: by 2002:a7b:cbc4:: with SMTP id n4mr1252171wmi.153.1622774877465; Thu, 03 Jun 2021 19:47:57 -0700 (PDT) Received: from ?IPv6:2a0a:1580:0:1::100c? (ovpn1.odiso.net. [2a0a:1580:2000::3f]) by smtp.gmail.com with ESMTPSA id f5sm5665142wrf.22.2021.06.03.19.47.56 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Jun 2021 19:47:57 -0700 (PDT) Message-ID: <2422013ee08dd4e3abb04ba5360a084beddf5183.camel@odiso.com> From: aderumier@odiso.com To: pve-devel Date: Fri, 04 Jun 2021 04:47:55 +0200 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.061 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] ceph create pool with min_size=1 not possible anymore with last gui wizard X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2021 02:48:06 -0000 Hi, 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. Some users with small cluster/budgets want to do only size=2, so with min_size=2, the cluster will go read only in case of any osd down. It could be great to allow at least min_size=1 when size=2 is used. also, Other setup like size=4, min_size=2, also display the warning, but allow to validate the form. I'm not sure this warning is correct in this case , as since octopus, min_size is auto compute when pool is created, and a simple ceph osd pool create mypool 128 --size=4 , create a pool with min_size=2 by default.