public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Óscar de Arriba" <oscar@dearriba.es>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>,
	alain.pean@c2n.upsaclay.fr
Subject: Re: [PVE-User] Thin LVM showing more used space than expected
Date: Wed, 28 Dec 2022 12:19:31 +0100	[thread overview]
Message-ID: <41f85334-834c-4534-916d-39bf5e382c75@app.fastmail.com> (raw)
In-Reply-To: <5b795a94-ebd3-7793-a7c3-4567cd1b04f0@c2n.upsaclay.fr>

Hi Alain,

Thanks for taking time to answer my message.
I think Proxmox UI is showing the % of wearout consumed. I just checked SMART using smartctl and it is showing 2.86 TB witten of a maximum of 180 TBW of this model (6%).

I think those numbers are too much for the usage of this drive, but the number of power on hours match (52 days). I think the TBW are elevated because we had an instance with swap actived and that could generate s lot of IO (that's no longer the case from a couple of weeks ago).

However, the strange behaviour of showing much more space used than the sum of VM disks + snapshots continue, and I'm really worried that the performance issue after copying some data can come from that situation. Also, the unit is showing now a 96% of space used, which worries me about decreased performance because of fragmentation issues.

Oscar

On Wed, Dec 28, 2022, at 11:52, Alain Péan wrote:
> Le 27/12/2022 à 18:54, Óscar de Arriba a écrit :
> > For storage, I'm using a commercial Crucial MX500 SATA SSD connected directly to the motherboard controller (no PCIe HBA for the system+data disk) and it is brand new - and S.M.A.R.T. checks are passing, only 4% of wearout.
> 
> Hi Oscar,
> 
> Just to be sure, because normally wearout is 100% when the SSD is new, 
> You are just soustracting, and it is in fact 100-4 = 96% ?
> My SSDs (Dell mixed use) after some years are still at 99%, so I am 
> wondering about 4%...
> 
> 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
> 
> 


  reply	other threads:[~2022-12-28 11:26 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 [this message]
2022-12-28 12:17     ` Alain Péan
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=41f85334-834c-4534-916d-39bf5e382c75@app.fastmail.com \
    --to=oscar@dearriba.es \
    --cc=alain.pean@c2n.upsaclay.fr \
    --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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal