From: David der Nederlanden | ITTY via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: David der Nederlanden | ITTY <david@itty.nl>
Subject: Re: [PVE-User] [Extern] - Re: "nearfull" status in PVE Dashboard not consistent
Date: Tue, 10 Sep 2024 18:32:19 +0000 [thread overview]
Message-ID: <mailman.166.1725994100.414.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <f264ef8d-f8ee-4011-91ca-7454f2449350@dkfz-heidelberg.de>
[-- Attachment #1: Type: message/rfc822, Size: 12152 bytes --]
From: David der Nederlanden | ITTY <david@itty.nl>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: RE: [PVE-User] [Extern] - Re: "nearfull" status in PVE Dashboard not consistent
Date: Tue, 10 Sep 2024 18:32:19 +0000
Message-ID: <AM8P193MB1139009B3EB1F017922B2610B89A2@AM8P193MB1139.EURP193.PROD.OUTLOOK.COM>
In hindsight, after reading some more about this, I don't think this is relevant.
-----Oorspronkelijk bericht-----
Van: pve-user <pve-user-bounces@lists.proxmox.com> Namens Frank Thommen
Verzonden: Tuesday, September 10, 2024 14:13
Aan: pve-user@lists.proxmox.com
Onderwerp: Re: [PVE-User] [Extern] - Re: "nearfull" status in PVE Dashboard not consistent
How/where can I see that? All commands that I found so far, only print out size and/or usage of the OSDs themselves. Also with LVM commands I only managed to see the size of the DB LVs, but not the current usage.
On 09.09.24 23:01, David der Nederlanden | ITTY via pve-user wrote:
> Thanks, the used procedure seems solid.
>
> In addition, how full are your DB/WAL drives?
>
> Kind regards,
> David
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
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-10 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2024-09-09 0:46 ` [PVE-User] " Bryan Fields
2024-09-10 11:48 ` [PVE-User] [Extern] - " Frank Thommen
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=mailman.166.1725994100.414.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=david@itty.nl \
/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.