From: Frank Thommen <f.thommen@dkfz-heidelberg.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] [Extern] - Re: "nearfull" status in PVE Dashboard not consistent
Date: Wed, 11 Sep 2024 13:00:06 +0200 [thread overview]
Message-ID: <04e0a0b2-2941-456e-9bef-0d360623ca08@dkfz-heidelberg.de> (raw)
In-Reply-To: <mailman.169.1725995190.414.pve-user@lists.proxmox.com>
The OSDs are of different size, because we have 4 TB and 2 TB disks in
the systems.
We might give the reweight a try.
On 10.09.24 20:31, David der Nederlanden | ITTY via pve-user wrote:
> Hi Frank,
>
> The images didn't work 🙂
>
> Pool and osd nearfull are closely related, when OSD's get full your pool
> also gets nearfull as Ceph needs to be able to follow the crush rules,
> which it can't if one of the OSD's gets full, hence it warns when it
> gets nearfull.
>
> I see that you're mixing OSD sizes, deleting and recreating the OSD's
> one by one caused this, as the OSD's got new weights you should be OK
> when you reweight them.
> You can do this by hand or using reweight-by-utilization, what you
> prefer.
>
> Not quite sure about the pool sizes, but an RBD pool with a 2/3 min/max
> rule should never be above 80%, as this gives you a nearfull pool when
> it starts backfilling when you lose one node, or even a full pool worst
> case, rendering the pool read only.
>
> Kind regards,
> David
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-09-11 11:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 19:04 [PVE-User] " Frank Thommen
2024-09-07 19:07 ` Frank Thommen
2024-09-07 19:14 ` Frank Thommen
2024-09-07 19:27 ` David der Nederlanden | ITTY via pve-user
2024-09-07 19:49 ` Peter Eisch via pve-user
2024-09-08 12:17 ` [PVE-User] [Extern] - " Frank Thommen
2024-09-09 10:36 ` Eneko Lacunza via pve-user
2024-09-10 12:02 ` Frank Thommen
2024-09-10 18:31 ` David der Nederlanden | ITTY via pve-user
2024-09-11 11:00 ` Frank Thommen [this message]
2024-09-11 11:52 ` Daniel Oliver
2024-09-11 14:24 ` Frank Thommen
2024-09-11 14:22 ` Frank Thommen
2024-09-11 10:51 ` Frank Thommen
2024-09-08 12:17 ` [PVE-User] " Frank Thommen
2024-09-09 0:46 ` Bryan Fields
2024-09-10 11:48 ` [PVE-User] [Extern] - " Frank Thommen
2024-09-09 21:01 David der Nederlanden | ITTY via pve-user
2024-09-10 12:12 ` Frank Thommen
2024-09-10 18:32 ` David der Nederlanden | ITTY via pve-user
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=04e0a0b2-2941-456e-9bef-0d360623ca08@dkfz-heidelberg.de \
--to=f.thommen@dkfz-heidelberg.de \
--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