From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Humberto Jose de Sousa <humbertos@ifsc.edu.br>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] SPAM: Re:
Date: Tue, 25 Jul 2023 09:47:16 +0200 [thread overview]
Message-ID: <47684dd6-6e30-dcdb-7e36-c4566ea08820@proxmox.com> (raw)
In-Reply-To: <CAGehcqHiwKabU9pvRbD_9POTqTq3kGv26zJWBEYDkA+DpsEmVg@mail.gmail.com>
On 7/24/23 19:17, Humberto Jose de Sousa wrote:
> Hi Aaron,
>
> It was OSDs Bluestore.
> I tried only `ceph-volume simple scan /dev/sdx` and it didn't work.
"simple" is for legacy file store OSDs :)
> In the end I decided to destroy and recreate.
>
> This problem only occurred with one of the five updates. I didn't
> understand ...
>
> Thanks!
> Em seg., 24 de jul. de 2023 às 05:58, Aaron Lauterer <a.lauterer@proxmox.com>
> escreveu:
>
>> Are those OSDs bluestore ones or still old file-store ones?
>>
>> Have you tried running `ceph-volume lvm activate --all`?
>>
>> It should search for bluestore OSDs and activate them. Activating means,
>> mounting the tmpfs into the /var/lib/ceph/osd/ceph-{id} and starting the
>> systemd
>> units.
>>
>> On 7/21/23 21:56, Humberto Jose de Sousa wrote:
>>> Hi folks,
>>>
>>> I upgraded my ceph cluster from Octopus to Pacific and Pacific to Quincy,
>>> no problems here.
>>>
>>> So I upgraded pve 7 to 8. After reboot the OSDs don't up. There is no
>>> directory /etc/ceph/osd/ and json files. The directory
>>> /var/lib/ceph/osd/ceph-<id>/ is empty.
>>>
>>> How can I recreate the lost files?
>>
>>
>
prev parent reply other threads:[~2023-07-25 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGehcqHmTqfjBRwt61hWjjA1CQm8inajfS0=EOqCPrAdmGUheA@mail.gmail.com>
2023-07-24 8:58 ` [PVE-User] (no subject) Aaron Lauterer
[not found] ` <CAGehcqHiwKabU9pvRbD_9POTqTq3kGv26zJWBEYDkA+DpsEmVg@mail.gmail.com>
2023-07-25 7:47 ` Aaron Lauterer [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=47684dd6-6e30-dcdb-7e36-c4566ea08820@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=humbertos@ifsc.edu.br \
--cc=pve-user@lists.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