From: Branislav Viest <info@branoviest.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Ceph: sudden slow ops, freezes, and slow-downs
Date: Wed, 22 Jun 2022 20:39:45 +0200 (CEST) [thread overview]
Message-ID: <1918332790.5860.1655923185691.JavaMail.zimbra@branoviest.com> (raw)
Hello,
I have experienced some serious difficulties with our Ceph cluster built-in from 4 nodes. I have created a proxmox forum topic regarding this problem and I think it is useless to type all the information in this mailing thread. I would like to ask you guys to check it out and if anyone has any idea what should cause this problem, what should be a problem, or how to solve it, I would be very sincere and thankful. Any idea or your experience is worthy.
We have already begun the migration process to another provider but I want to know the answer or the problem roots anyway to prevent possible failure or problems after migration.
The topic is here: [ https://forum.proxmox.com/threads/ceph-sudden-slow-ops-freezes-and-slow-downs.111144/ | https://forum.proxmox.com/threads/ceph-sudden-slow-ops-freezes-and-slow-downs.111144/ ]
Thank you all.
------------
Best Regards
Branislav Brian Viest
linux administrator
------------
Legal Disclaimer: This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this e-mail. The sender does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of or reliance on the information. All e-mail messages addressed to, received or sent by sender are deemed to be professional in nature. Accordingly, the sender or recipient of these messages agrees that they may be read by other sender employees than the official recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof.
next reply other threads:[~2022-06-22 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 18:39 Branislav Viest [this message]
[not found] ` <mailman.54.1655965821.338.pve-user@lists.proxmox.com>
2022-06-23 6:54 ` Branislav Viest
[not found] ` <4c507d5f-5ad9-9fb1-6eab-6ca1913784d8@binovo.es>
2022-06-23 8:24 ` Branislav Viest
[not found] ` <1cdc99da-0537-7533-2987-8678223e2971@binovo.es>
2022-06-23 13:54 ` Branislav Viest
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=1918332790.5860.1655923185691.JavaMail.zimbra@branoviest.com \
--to=info@branoviest.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox