From: "Alain péan" <alain.pean@c2n.upsaclay.fr>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Fwd: [ceph-users] [IMPORTANT NOTICE] Potential data corruption in Pacific
Date: Thu, 28 Oct 2021 19:14:33 +0200 [thread overview]
Message-ID: <552796a1-e2af-d83b-975d-1a3fe393e8db@c2n.upsaclay.fr> (raw)
In-Reply-To: <mailman.67.1635437996.15957.pve-user@lists.proxmox.com>
Le 28/10/2021 à 18:19, Eneko Lacunza via pve-user a écrit :
> Hi,
>
> Regarding this important issue reported for Ceph (just
> cross-forwarding for those Ceph users not in ceph-user list):
>
> 1. Proxmox upgrade wiki page
> https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific marks as optional
> disabling the conversion with "ceph config set osd
> bluestore_fsck_quick_fix_on_mount false", and urges to convert ASAP.
> It is now advised not to perform the conversion until a fix is released.
>
> 2. We have upgraded 2 clusters, but both have
> bluestore_fsck_quick_fix_on_mount set to false. No command setting
> that flag in our server's history, so I don't think we set that (I
> wasn't the admin performin the upgrade, I'll be able to check with her
> tomorrow)
>
> 3. Is it possible that for ceph 16.2.6
> bluestore_fsck_quick_fix_on_mount default value is false?
>
> I expect an emergency fix released soon but I guess checking won't
> hurt anyone ;)
Hi Eneko,
Thanks for the warning. I saw the thread on ceph-users mailing list.
Personnally, I upgraded my clusters from PVE 6.4 to 7.0, but not yet
from Nautilus to Pacific. I'll wait a bit for this.
Also, I have one cluster (the one in production) that is still with
filestore OSDs. I was wondering, considering '
bluestore_fsck_quick_fix_on_mount", if it was mandatory to have
bluestore OSDs on Pacific.
Personnally, when I see that you have to manually destroy your OSDs one
after the other, then recreate it as bluestore, I am a bit reluctant to
do the upgrade...
Let's see !
Alain
--
Administrateur Système/Réseau
C2N (ex LPN) Centre de Nanosciences et Nanotechnologies (UMR 9001)
10 Boulevard Thomas Gobert (ex Avenue de la Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88
next parent reply other threads:[~2021-10-28 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3765b095-5a5d-1e32-5e44-b11e2c2047ed@croit.io>
[not found] ` <mailman.67.1635437996.15957.pve-user@lists.proxmox.com>
2021-10-28 17:14 ` Alain péan [this message]
[not found] ` <6a8d705a-32a7-b960-29a2-2bc0874fc215@binovo.es>
2021-10-29 11:55 ` Aaron Lauterer
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=552796a1-e2af-d83b-975d-1a3fe393e8db@c2n.upsaclay.fr \
--to=alain.pean@c2n.upsaclay.fr \
--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