From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Marco Gaiarin <gaio@lilliput.linux.it>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Analysis of free space...
Date: Fri, 26 Sep 2025 16:57:40 +0200 [thread overview]
Message-ID: <28miql-d0b2.ln1@leia.lilliput.linux.it> (raw)
In-Reply-To: <4d28ql-5ua2.ln1@leia.lilliput.linux.it>; from SmartGate on Sat, Sep 27, 2025 at 18:06:01PM +0200
> Uh, wait... effectively we forgot to enable 'discard' on volumes, and we have
> enabled afterward (but rebooted the VM).
Still here. I've rechecked every passage and i summarize here:
1) ZFS storage had 'Thin provision' enabled from the start
2) we create a bounch of volumes for the VM, and, using LVM, bind that on some
logical volumes XFS formatted. 'discard' was not checked.
3) we delete roughly 20+TB of data from VM, we try to copy some more data on
VM volumes but storage fill up.
4) we enabled 'discard' on volumes, reboot VM and phisical node, do some
manual trim: some TB get freed, but not 20+TB.
5) we find another 8TB of junk data and delete them; after that, we do a
manual trim that freed 8TB on storage.
Evidently data copied (and deleted) on voluems before we set 'discard=on'
are not managed by trim, and we need in some way to force some FS
'rescan'...
How? Thanks.
--
_______________________________________________
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-27 16:10 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
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 [this message]
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=28miql-d0b2.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--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