From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>,
"pve-user@pve.proxmox.com" <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] Fwd: [ceph-users] [IMPORTANT NOTICE] Potential data corruption in Pacific
Date: Fri, 29 Oct 2021 13:55:44 +0200 [thread overview]
Message-ID: <1337e488-b458-79e2-8c46-29c4727fc558@proxmox.com> (raw)
In-Reply-To: <6a8d705a-32a7-b960-29a2-2bc0874fc215@binovo.es>
Thank you for bringing this to our attention.
I did a test on a freshly installed PVE 7 + Octopus cluster and there the `bluestore_fsck_quick_fix_on_mount` was set to true... That's why I updated the upgrade guide [0]. Checking the setting before upgrading and if true, setting it to false, should be okay IIUC.
Once we release a version with a fix we will update the guide again to reflect the new situation.
Thanks!
Aaron
[0] https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific
On 10/28/21 18:19, Eneko Lacunza wrote:
> 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 ;)
>
> Thanks
> Eneko
>
>
>
> EnekoLacunza
>
> CTO | Zuzendari teknikoa
>
> Binovo IT Human Project
>
> 943 569 206 <tel:943 569 206>
>
> elacunza@binovo.es <mailto:elacunza@binovo.es>
>
> binovo.es <//binovo.es>
>
> Astigarragako Bidea, 2 - 2 izda. Oficina 10-11, 20180 Oiartzun
>
>
> youtube <https://www.youtube.com/user/CANALBINOVO/>
> linkedin <https://www.linkedin.com/company/37269706/>
>
prev parent reply other threads:[~2021-10-29 12:02 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
[not found] ` <6a8d705a-32a7-b960-29a2-2bc0874fc215@binovo.es>
2021-10-29 11:55 ` 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=1337e488-b458-79e2-8c46-29c4727fc558@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=elacunza@binovo.es \
--cc=pve-user@pve.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