public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Óscar de Arriba" <oscar@dearriba.es>
To: "Martin Holub" <martin@holub.co.at>, pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Thin LVM showing more used space than expected
Date: Thu, 29 Dec 2022 11:48:16 +0100	[thread overview]
Message-ID: <64119642-e2a3-428a-a053-371f9fc6bda0@app.fastmail.com> (raw)
In-Reply-To: <b462e244-86a1-eada-c50b-4361f037dc1e@holub.co.at>

Any idea why it still has 96.23% of space used but the VMs are using way less? I'm starting to worry a lot about it (I don't kant tobe really full) and my current only hope is backup + reinstall PVE.

Thanks,
Oscar

On Thu, Dec 29, 2022, at 11:01, Martin Holub wrote:
> 
> 
> Am 28.12.2022 um 12:44 schrieb Óscar de Arriba:
>> Hi Martin,
>> 
>> > Did you try to run a fstrim on the VMs to regain the allocated space? At least on linux something like "fstrim -av" should do the trick.
>> 
>> I did it now and it freed ~55GiB of a running isntance (the one with 128 GiB allocated). However that should only free blocks of the LV used to store that VM disk, right? And the issue itself is that the sum of maximum allocations of those disks is much lower than the space occupied.
>> 
>> I also have the feeling that those blocks remain used by a no longer existant LVs, but I don't know how to fix it.
>> 
>> Should I also enable trim/execute trim on Proxmox itself?
>> 
>> Oscar
>> 
> 
> 
> 
> Hi,
> 
> TRIM only works on a filesystem level, so you can't trim a VG or similar. On the pve host i doubt it will help, but it wouldn't harm either. 
> 
> hth
> Martin
> 


  parent reply	other threads:[~2022-12-29 10:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2022-12-29 16:58       ` Óscar de Arriba
2022-12-30  9:52         ` Tom Weber
2023-01-02  9:56         ` Óscar de Arriba
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
2022-12-28 18:22       ` Ó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=64119642-e2a3-428a-a053-371f9fc6bda0@app.fastmail.com \
    --to=oscar@dearriba.es \
    --cc=martin@holub.co.at \
    --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