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 3ED38635BB for ; Wed, 25 Nov 2020 09:27:25 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3003F16479 for ; Wed, 25 Nov 2020 09:26:55 +0100 (CET) Received: from mail.merit.unu.edu (mail.merit.unu.edu [192.87.143.6]) by firstgate.proxmox.com (Proxmox) with ESMTP id AB6D51646C for ; Wed, 25 Nov 2020 09:26:54 +0100 (CET) Received: from [192.168.89.63] (77-3-157-94.ftth.glasoperator.nl [94.157.3.77]) by mail.merit.unu.edu (Postfix) with ESMTPSA id 98AD480601BCF for ; Wed, 25 Nov 2020 09:18:42 +0100 (CET) To: pve-user@lists.proxmox.com From: mj Message-ID: Date: Wed, 25 Nov 2020 09:18:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.582 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [PVE-User] confirmation on osd replacement X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 08:27:25 -0000 Hi, I would just like to verify/confirm something here, as we are going to replace our spinning OSDs with SSDs. We have 8 OSDs per server, and two empty front driveslots available. The proxmox boot disk is internal, and currently known as /dev/sdk Suppose I insert two new SSDs in the (two empty) front drive bays, I expect the internal boot disk to shift from /dev/sdk to /dev/sdm The questions: - should we expect boot problems or other side-effects of doing that? (of course I will test on the first server, I'd just like to know what to expect) And then I am going to first add per server two new bluestore SSDs, making a (temporarily) total of 10 OSDs per server. And then I want to replace the 8 remaining filestore spinning OSDs with 6 bluestore SSDs. Making again a total of 8 OSDs per server. The idea is: first add two SSDs to increase IO capacity for the rest of the procedure, while at the same time reducing stress on our filestore journal SSD (wear level=75%) Any comments? MJ