From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Analysis of free space...
Date: Thu, 9 Oct 2025 22:46:52 +0200 [thread overview]
Message-ID: <aOgfPKmSK24CLI7q@sv.lnf.it> (raw)
In-Reply-To: <83a699e14058057ed3467637dc2f2e1fa4199a08@antreich.com>
Mandi! Alwin Antreich
In chel di` si favelave...
>> OK. But this can explain some data, not 20TB of not reclaimed space; and, as
>> just stated, if i delete now (after that i've set discard=on on volume
>> property) data, space get correctly reclaimed.
>
> The parity is calculated for data written and by the docs [0], it is 8K zvol
> block + 4K parity (50%). See also the openzfs docs [1].
> By that calculation you'll need 512 GB for every 1 TB written. That means that
> the 2TB disk will use 3TB on ZFS, plus some extra.
No, sorry; effective space used was a curiosity, not my real question. Sorry
for the misunderstanding.
As just stated:
0) zraid storage created with 'thin provision' enabled.
1) create a bunch of 2TB volumes for a VM, forgot to enable 'discard'.
2) fill VM with DATA
3) delete data from VM.
4) fill again VM with data, space exausted.
5) ops! we have forgot to enable 'discard', enabled it.
6) delete more data (8TB), trim volumes: space reclaimed, but only this 8TB
of data, not the data on point 2.
How can i 'force' some sort of rescan of volumes so trim can happen? Seems
to me that only data deleted after 5) can be reclaimed, the other not.
Actually VM have 20TB of data, pool have 55TB of data. 30TB is expectd, not
55...
I hope i was clear now.
--
Marco ``Gaio'' Gaiarin | Pordenone Linux User Group (https://www.pnlug.it/)
P.zza S. Tommaso, 20 | Lilliput BBS (http://bbs.lilliput.linux.it)
Cimpello di Fiume Veneto | Azione Cattolica - Concordia-Pordenone
33080 Pordenone (Italia) | (https://www.acconcordiapn.it/)
Tel. +39-0434-56-1305 | Mastodon:@marcogaio@sociale.network gaio@linux.it
_______________________________________________
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-10-09 20:50 UTC|newest]
Thread overview: 17+ 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-10-01 14:03 ` Alwin Antreich via pve-user
2025-10-06 11:32 ` Marco Gaiarin
2025-10-09 20:21 ` Alwin Antreich via pve-user
[not found] ` <83a699e14058057ed3467637dc2f2e1fa4199a08@antreich.com>
2025-10-09 20:46 ` Marco Gaiarin [this message]
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=aOgfPKmSK24CLI7q@sv.lnf.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 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.