From: Harald Leithner <leithner@itronic.at>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] Ceph 16 upgrade warning also valid for proxmox users?
Date: Thu, 18 Nov 2021 19:02:44 +0100 [thread overview]
Message-ID: <dd386363-bfb9-25eb-6246-d4dbbeabe9a6@itronic.at> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1305 bytes --]
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/
--
DATE: 01 NOV 2021.
DO NOT UPGRADE TO CEPH PACIFIC FROM AN OLDER VERSION.
A recently-discovered bug (https://tracker.ceph.com/issues/53062) can
cause data corruption. This bug occurs during OMAP format conversion for
clusters that are updated to Pacific. New clusters are not affected by
this bug.
The trigger for this bug is BlueStore’s repair/quick-fix functionality.
This bug can be triggered in two known ways:
manually via the ceph-bluestore-tool, or
automatically, by OSD if bluestore_fsck_quick_fix_on_mount is set to true.
The fix for this bug is expected to be available in Ceph v16.2.7.
DO NOT set bluestore_quick_fix_on_mount to true. If it is currently set
to true in your configuration, immediately set it to false.
DO NOT run ceph-bluestore-tool’s repair/quick-fix commands.
--
thanks
Harald
--
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 reply other threads:[~2021-11-18 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 18:02 Harald Leithner [this message]
2021-11-19 7:42 ` Dominik Csapak
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=dd386363-bfb9-25eb-6246-d4dbbeabe9a6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox