From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Ceph 16 upgrade warning also valid for proxmox users?
Date: Fri, 19 Nov 2021 08:42:56 +0100 [thread overview]
Message-ID: <dc02fdb3-e9a2-3094-2eb2-ba7a49220cbd@proxmox.com> (raw)
In-Reply-To: <dd386363-bfb9-25eb-6246-d4dbbeabe9a6@itronic.at>
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
next prev parent reply other threads:[~2021-11-19 7:43 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 [this message]
2021-11-19 8:46 ` Harald Leithner
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=dc02fdb3-e9a2-3094-2eb2-ba7a49220cbd@proxmox.com \
--to=d.csapak@proxmox.com \
--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.