From: "Alain Péan" <alain.pean@c2n.upsaclay.fr>
To: "Óscar de Arriba" <oscar@dearriba.es>,
"Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Thin LVM showing more used space than expected
Date: Wed, 28 Dec 2022 13:17:02 +0100 [thread overview]
Message-ID: <8f8156db-ec51-a426-3146-3fcf843b5699@c2n.upsaclay.fr> (raw)
In-Reply-To: <41f85334-834c-4534-916d-39bf5e382c75@app.fastmail.com>
Le 28/12/2022 à 12:19, Óscar de Arriba a écrit :
> I think Proxmox UI is showing the % of wearout consumed.
In my case, with Dell servers, the UI in fact is not showing anything
(N/A), when the Raid storage volume is managed by the raid controller.
In this case, I use Dell OMSA (Open Manage Server Administration), to
display the values.
But I have another cluster with Ceph, and indeed, it displays 0% as
wearout. So I think you are right.
I saw that they are Crucial SATA SSD directly attached on the
motherboard. What kind of filesystem do you have on these SSDs ? Can you
run pveperf on /dev/mapper/pveroot to see what are the performances ?
Alain
--
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88 Bureau A255
next prev parent reply other threads:[~2022-12-28 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 17:54 Óscar de Arriba
2022-12-28 10:52 ` Alain Péan
2022-12-28 11:19 ` Óscar de Arriba
2022-12-28 12:17 ` Alain Péan [this message]
2022-12-28 18:22 ` Óscar de Arriba
[not found] <mailman.3.1672225201.17323.pve-user@lists.proxmox.com>
2022-12-28 11:44 ` Óscar de Arriba
[not found] ` <b462e244-86a1-eada-c50b-4361f037dc1e@holub.co.at>
2022-12-29 10:48 ` Óscar de Arriba
2022-12-29 16:58 ` Óscar de Arriba
2022-12-30 9:52 ` Tom Weber
2023-01-02 9:56 ` Óscar de Arriba
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=8f8156db-ec51-a426-3146-3fcf843b5699@c2n.upsaclay.fr \
--to=alain.pean@c2n.upsaclay.fr \
--cc=oscar@dearriba.es \
--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