From: Gilou <contact+dev@gilouweb.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Analysis of free space...
Date: Thu, 18 Sep 2025 01:45:41 +0200 [thread overview]
Message-ID: <4e2222b8-f423-41e3-a6fb-522a6f792f0b@gilouweb.com> (raw)
In-Reply-To: <cjpqpl-12t1.ln1@leia.lilliput.linux.it>
Le 17/09/2025 à 15:27, Marco Gaiarin a écrit :
>
> We have an PVE8 server, on clustered, with 66TB of disk storage and (for
> now) a single VM; volumes have all 'discard' option enabled, and the VM
> (RH8) support and have trim enabled.
>
> We moved around some data between volumes, and now we have 20TB used in the
> VM, and 56TB used on the zfs pool that host that volumes.
>
> Clearly we have done some manual 'trim' to be sure, but nothing changed (or,
> better, some space get reclaimed but not what we expect).
>
>
> There's some tool/methodology to find where data get stuck, and how?
Hi,
What's the underlying storage? local zfs?
Does it have thin provisioning / sparse enabled?
You can check that forum post:
https://forum.proxmox.com/threads/zfs-enable-thin-provisioning.41549/
Also inside the VM, make sure that all the stack is discard aware, LVM,
filesystem and all..
Regards,
Gilou
_______________________________________________
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:[~2025-09-17 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 13:27 Marco Gaiarin
2025-09-17 23:45 ` Gilou [this message]
2025-09-22 14:14 ` Marco Gaiarin
2025-09-22 14:17 ` Marco Gaiarin
2025-09-24 16:29 ` Marco Gaiarin
2025-09-27 15:42 ` Alwin Antreich via pve-user
2025-09-30 16:26 ` Marco Gaiarin
2025-09-27 16:06 ` Matthieu Dreistadt via pve-user
2025-09-30 16:55 ` Marco Gaiarin
2025-09-26 14:57 ` Marco Gaiarin
2025-09-18 13:44 ` Alwin Antreich via pve-user
2025-09-22 14:16 ` Marco Gaiarin
2025-09-25 8:26 ` Marco Gaiarin
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=4e2222b8-f423-41e3-a6fb-522a6f792f0b@gilouweb.com \
--to=contact+dev@gilouweb.com \
--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