From: Harald Leithner <leithner@itronic.at>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Ceph 16 upgrade warning also valid for proxmox users?
Date: Fri, 19 Nov 2021 09:46:45 +0100 [thread overview]
Message-ID: <6d566e47-42cc-711e-60df-b9096f4df6c1@itronic.at> (raw)
In-Reply-To: <dc02fdb3-e9a2-3094-2eb2-ba7a49220cbd@proxmox.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1377 bytes --]
Hi,
thanks Dominik for the heads up on the upgrade documentation.
Also thanks to Eneko Lacunza for sharing his experience.
Since I have no hurry to update we will wait till 16.2.7 is released.
Harald
Am 19.11.2021 um 08:42 schrieb Dominik Csapak:
> On 11/18/21 19:02, Harald Leithner wrote:
>> Hi,
>>
>> the ceph release packages site has a big red warning not to upgrade
>> from earlier versions to Pacific.
>>
>> So when I haven't updated to Pacific yet, should I wait or is it safe
>> to upgrade for what ever reason?
>>
>> https://docs.ceph.com/en/latest/releases/pacific/
>
> Hi,
>
> this bug is already mentioned in our upgrade guide:
>
> https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific#Check_if_bluestore_fsck_quick_fix_on_mount_is_disabled
>
>
> You can ofc run Octopus for now, if you want to play it safe and wait
> for a fix in Pacific (though AFAIK if that option is disabled the
> upgrade should be ok, but maybe i am missing something)
>
> kind regards
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
--
ITronic
Harald Leithner
Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Mobil: +43-699-123 78 4 78
Mail: leithner@itronic.at | itronic.at
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
next prev parent reply other threads:[~2021-11-19 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 18:02 Harald Leithner
2021-11-19 7:42 ` Dominik Csapak
2021-11-19 8:46 ` Harald Leithner [this message]
2021-11-19 13:11 ` Lindsay Mathieson
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=6d566e47-42cc-711e-60df-b9096f4df6c1@itronic.at \
--to=leithner@itronic.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.