From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-user-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id CEF991FF29E for <inbox@lore.proxmox.com>; Sun, 30 Jun 2024 20:44:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 211FD1A0D0; Sun, 30 Jun 2024 20:44:40 +0200 (CEST) Date: Sun, 30 Jun 2024 18:44:03 +0000 To: "Proxmox VE user list" <pve-user@lists.proxmox.com> In-Reply-To: <CAOKSTBsRMB5fQ8iU9VXLwYjQ38yN1mvPP6mCg-WSAguAptSjEA@mail.gmail.com> References: <mailman.168.1719760115.331.pve-user@lists.proxmox.com> <CAOKSTBsRMB5fQ8iU9VXLwYjQ38yN1mvPP6mCg-WSAguAptSjEA@mail.gmail.com> MIME-Version: 1.0 Message-ID: <mailman.169.1719773078.331.pve-user@lists.proxmox.com> List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Post: <mailto:pve-user@lists.proxmox.com> From: Peter Eisch via pve-user <pve-user@lists.proxmox.com> Precedence: list Cc: Peter Eisch <peter@boku.net> X-Mailman-Version: 2.1.29 X-BeenThere: pve-user@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> Subject: Re: [PVE-User] CEPH migration from cephadm or keep cephadm? Content-Type: multipart/mixed; boundary="===============1386286988480654687==" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" <pve-user-bounces@lists.proxmox.com> --===============1386286988480654687== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <peter@boku.net> X-Original-To: pve-user@lists.proxmox.com Delivered-To: pve-user@lists.proxmox.com 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 201EABAEE9 for <pve-user@lists.proxmox.com>; Sun, 30 Jun 2024 20:44:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EFDC319F5E for <pve-user@lists.proxmox.com>; Sun, 30 Jun 2024 20:44:07 +0200 (CEST) Received: from mail.boku.net (mail.boku.net [204.130.132.5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Sun, 30 Jun 2024 20:44:05 +0200 (CEST) Comment: DomainKeys? See http://domainkeys.sourceforge.net/ DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=boku.net; b=b30xOH6yiPtCktxThqKPKgFqiKfkOE/kMccbyiwOn5qDGODylXdAXmOdmwYfBySqnMrnolYrHKOa/JGzgwL77DtmCjMy+6CXtJy6G30R0nqhTKf+1qu8Ik+8qu/z4EMr8ti+mRfw9s3NYw/FSYbGauOxTDKj4/FmiwHWZpC/+YU=; h=Received:Received:Mime-Version:Date:Content-Type:Message-ID:X-Mailer:From:Subject:To:X-Draft-Info:In-Reply-To:References:X-Priority; DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=boku.net; h=mime-version :date:content-type:message-id:from:subject:to:in-reply-to :references; s=default; bh=oXI8MeZk8flQsV6bKL61lqtUnDo=; b=WReGF rX8Z47O2DnbskTAx3lU3L0k5bBMTLj0COypBDa1mBmwg8C3wN6zlnM4QdhOTGa3N LR5TDr10GoUs78Nojl/vsfuFFF2oADiIIt5RTA3BzQziDzCvEWrUQrfeg7QX00aa FXAJqChBNnVoGiUVIDsZSrk+s+VLxskR9DqmoQ= Received: (qmail 19914 invoked by uid 500); 30 Jun 2024 18:44:03 -0000 Received: from unknown (HELO mail.boku.net) (127.0.0.1) by qmail6.boku.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 30 Jun 2024 18:44:03 -0000 Mime-Version: 1.0 Date: Sun, 30 Jun 2024 18:44:03 +0000 Message-ID: <b2162682b42137edb315f307645a10f4@mail.boku.net> X-Mailer: AfterLogic webmail client From: "Peter Eisch" <peter@boku.net> Subject: Re[2]: [PVE-User] CEPH migration from cephadm or keep cephadm? To: "Proxmox VE user list" <pve-user@lists.proxmox.com> X-Draft-Info: type="reply-all"; uid="276414"; folder="SU5CT1g=" In-Reply-To: <CAOKSTBsRMB5fQ8iU9VXLwYjQ38yN1mvPP6mCg-WSAguAptSjEA@mail.gmail.com> References: <mailman.168.1719760115.331.pve-user@lists.proxmox.com> <CAOKSTBsRMB5fQ8iU9VXLwYjQ38yN1mvPP6mCg-WSAguAptSjEA@mail.gmail.com> X-Priority: 3 (Normal) X-SPAM-LEVEL: Spam detection results: 0 AWL 0.500 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy HTML_MESSAGE 0.001 HTML included in message SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 It largely works. At some point this issue crept in:=0Aroot@node3:/# cep= h-volume inventory=0A stderr: Unknown device "/dev/pve/data_tmeta": No s= uch device=0A stderr: Unknown device "/dev/pve/data_tdata": No such devi= ce=0A stderr: Unknown device "/dev/pve-data/tpool": No such device=0A s= tderr: Unknown device "/dev/pve/data": No such device=0A --> KeyError: '= TYPE'=0A root@node3:/# =0Awhich seems to be tied to lvmthin. This thread= https://www.spinics.net/lists/ceph-users/msg79647.html (https://www.spin= ics.net/lists/ceph-users/msg79647.html) had solution to this but not a PV= E issue.=0AThanks for the confirmation.=0A=0AOn Sun, Jun 30, 2024 at 10:4= 1 AM, Gilberto Ferreira wrote: =0AHi there=0AIf it's works, keep it just= like that.=0AEm dom., 30 de jun. de 2024 =C3=A0s 12:08, Peter Eisch via = pve-user escreveu:=0A---------- Forwarded message ----------=0AFrom: Pet= er Eisch =0ATo: pve-user@lists.proxmox.com (mailto:pve-user@lists.proxmox= .com)=0ACc: =0ABcc: =0ADate: Sun, 30 Jun 2024 15:08:31 +0000=0ASubject: C= EPH migration from cephadm or keep cephadm?=0AHi,=0A I have a CEPH cluste= r where I=E2=80=99ve been doing hyperconverged with Linux KVM. I have ha= d no problem migrating the VMs to PVE running on compute-only nodes. No = instances remain on the storage nodes.=0A Back to converged with:=0A=0A -= CEPH 18.2.2=0A=0A - cephadm orchestration=0A=0A - 6 hosts with 16 OSDs= each=0A=0A - 4 hosts rocky linux=0A=0A - 1 host PVE 8.2.2, deployed = OSDs with cephadm=0A=0A - 1 host out of the cluster, pending options=0A= =0A - 4 hosts running PVE/RBD=0A Is there a way to convert a cephadm CEPH= cluster to PVE=E2=80=99s CEPH? Is it better to keep cephadm?=0A Thank y= ou for your thoughts,=0A peter=0A---------- Forwarded message ----------= =0AFrom: Peter Eisch via pve-user =0ATo: pve-user@lists.proxmox.com (mail= to:pve-user@lists.proxmox.com)=0ACc: Peter Eisch =0ABcc: =0ADate: Sun, 30= Jun 2024 15:08:31 +0000=0ASubject: [PVE-User] CEPH migration from cephad= m or keep cephadm?=0A_______________________________________________=0A p= ve-user mailing list=0Apve-user@lists.proxmox.com (mailto:pve-user@lists.= proxmox.com)=0Ahttps://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-use= r (https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user) --===============1386286988480654687== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user --===============1386286988480654687==--