From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Cc: Alwin Antreich <alwin@antreich.com>
Subject: Re: [PVE-User] Analysis of free space...
Date: Thu, 18 Sep 2025 13:44:04 +0000 [thread overview]
Message-ID: <mailman.138.1758203495.390.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <cjpqpl-12t1.ln1@leia.lilliput.linux.it>
[-- Attachment #1: Type: message/rfc822, Size: 4612 bytes --]
From: "Alwin Antreich" <alwin@antreich.com>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Analysis of free space...
Date: Thu, 18 Sep 2025 13:44:04 +0000
Message-ID: <63783ca5c3f39fab913e615393ceea9c55bf147e@antreich.com>
Hi Marco,
September 17, 2025 at 3:27 PM, "Marco Gaiarin" <gaio@lilliput.linux.it mailto:gaio@lilliput.linux.it?to=%22Marco%20Gaiarin%22%20%3Cgaio%40lilliput.linux.it%3E > wrote:
>
> 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?
>
Are you running EXT4 on the guest?
https://forum.proxmox.com/threads/help-with-trim-on-virtio-scsi-single.123819/post-542552
Cheers,
Alwin
[-- 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
prev parent reply other threads:[~2025-09-18 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 13:27 Marco Gaiarin
2025-09-17 23:45 ` Gilou
2025-09-18 13:44 ` Alwin Antreich via pve-user [this message]
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.138.1758203495.390.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alwin@antreich.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 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.