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 12:51:15 +0200 [thread overview]
Message-ID: <6de43591-e77d-4f08-8629-f32ceecb2f22@dkfz-heidelberg.de> (raw)
In-Reply-To: <18d34454-78c8-4f31-9472-0db7cd17dbca@dkfz-heidelberg.de>
ok, here are - finally - the screenshots:
* from the Ceph overview dashboard: https://postimg.cc/fVJFstqW
* from the pool overview: https://postimg.cc/ykf52XPr
Frank
On 10.09.24 14:02, Frank Thommen wrote:
> Yes, but Ceph also reports five(!) nearfull pools, but the pool overview
> doesn't reflect that. I'd love to show this with CLI, but I could not
> find an appropriate command so far. Hopefully, inline images work:
>
> From the Ceph overview dashboard:
>
> And from the pool overview
>
> Two pools are quite full (80% and 82%), but far from nearfull, and the
> other tree are basically empty.
>
> Frank
>
>
> On 09.09.24 12:36, Eneko Lacunza via pve-user wrote:
>> Hi Frank,
>>
>> El 8/9/24 a las 14:17, Frank Thommen escribió:
>>> 5 hdd 3.81450 1.00000 3.8 TiB 3.3 TiB 3.1 TiB 37 MiB 8.5 GiB
>>> 568 GiB 85.45 1.16 194 up
>>> 16 hdd 1.90039 1.00000 1.9 TiB 1.6 TiB 1.6 TiB 19 MiB 5.4
>>> GiB 261 GiB 86.59 1.18 93 up
>>
>> Those OSD are nearfull, if you have the default 0.85 value for that.
>> You can try to lower a bit their weight.
>>
>> Cheers
>>
>> Eneko Lacunza
>> Zuzendari teknikoa | Director técnico
>> Binovo IT Human Project
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
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 10:51 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
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 [this message]
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=6de43591-e77d-4f08-8629-f32ceecb2f22@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.